PointClickCare API Guide (2026): USCDI Connector, Marketplace, Fees and Write-Back

Updated October 2026

PointClickCare has two ways in for outside software. The USCDI Connector gives you read access to standard FHIR R4 data, and the Marketplace partner program adds proprietary APIs, webhooks and a partner manager. Most of what decides cost and timeline sits in the agreement and in facility enablement, so this guide covers both alongside the API calls. It is written for product teams in long-term and post-acute care deciding whether and how to build. If you would rather have a team build it, see our PointClickCare integration services.

Every PointClickCare fact below comes from PointClickCare's own public pages, read on 28 October 2026, with the link next to it. Where we checked something ourselves against PointClickCare's public servers, we say so. Where PointClickCare publishes nothing (rate limits, Marketplace fees, review times for Marketplace apps), we say that too.

Short answers

• PointClickCare has a public FHIR R4 API, called the USCDI Connector. It follows SMART on FHIR and documents US Core 3.1.1 and the USCDI v1 data set.
• The USCDI Connector is read-only for clinical data. The only write the published spec allows is creating a Group for bulk export.
• Writing into PointClickCare (notes, admissions, assessments) and real-time change notifications (webhooks) are listed as Marketplace partner features. Those APIs are documented behind the partner login.
• PointClickCare's FHIR site says customers on its current pricing model pay a flat $65 per app, per facility, per month for USCDI Connector apps. The developer pays nothing to get access.
• Each PointClickCare customer enables your app facility by facility, with a Letter of Authorization. PointClickCare says enablement takes at least two weeks.
• The USCDI Connector agreement says the app may not be accessed or supported from outside the United States or Canada. Check this before you plan an offshore support team.

PointClickCare API facts at a glance (checked 28 October 2026)

Re-check any figure you plan a budget or a launch date around. PointClickCare says the $65 price is "subject to annual revision", and the agreement says the API sets "are subject to change from time to time".

Does PointClickCare have an API?

Yes. PointClickCare publishes a FHIR R4 API for the USCDI Connector at fhir.pointclickcare.com, with an open API specification and a published agreement. It also runs a partner program with proprietary REST APIs. The developer site describes "an evolving set of RESTful APIs, giving you access to user info, patient data, UI tools, notifications, and more" (Why PointClickCare). The proprietary API reference sits behind the developer portal login, so this guide cannot list its endpoints.

PointClickCare also states that "Vendors are required to access PCC systems through an authorized set of secure, modern, and governed channels" (Marketplace partnership inquiries). Plan on one of the two programs. Screen scraping and database copies are covered further down.

USCDI Connector or Marketplace partner: which one do you need?

PointClickCare's developer site compares the two programs in one table (Why PointClickCare, read 28 October 2026). In short:

The table marks "Development Sandbox" and "Community Forums" only in the Marketplace column. The FHIR site, though, says USCDI Connector development apps are "auto-approved and enabled in the PointClickCare FHIR Sandbox". So both programs get a sandbox for FHIR. The Marketplace adds sandbox access to the PointClickCare user interface.

A simple way to decide:

• You only need to read clinical data (problems, medications, allergies, vitals, notes as documents, care plans) for residents at facilities that have agreed to use your product. The USCDI Connector is enough.
• You need to write anything back, react to changes as they happen, sign users in with their PointClickCare account, or be listed where PointClickCare customers shop for products. You need the Marketplace partner program.
• You need census and financial data (bed moves, payer changes, billing). The USCDI Connector does not cover these. Ask about the Marketplace. Because the proprietary API reference is not public, we cannot confirm which census or billing fields it exposes.

PointClickCare's own description of the Marketplace is for companies "interested in working closely with PointClickCare to design, test, market, deploy, maintain, and support a certified interface" (Developer Program). Live Marketplace listings show what partners build: one sends clinical notes "directly to resident records", and another "sends admissions to PointClickCare" (Marketplace home). eClinicalWorks announced a Marketplace integration in March 2025 that transfers completed progress notes from eClinicalWorks into PointClickCare and pulls patient demographics the other way (eClinicalWorks press release). Our eClinicalWorks API guide covers the other side of that kind of connection.

How to get access, step by step

PointClickCare's FHIR site describes the path for the USCDI Connector (FHIR API home). The first step is the same for the Marketplace.

Step 1: apply for partnership

Fill in the "Apply for Partnership" form at marketplace.pointclickcare.com. The form asks for company size, a solution category (there are about 55, from "Admission Management" to "Wound Management"), whether you share a customer with PointClickCare, and your target market (acute care, skilled nursing, senior living). A PointClickCare partner manager then decides with you which program fits.

Step 2: create the developer portal account

Once the program is agreed, you get an emailed link to apply for a developer portal account. For the USCDI Connector, select "USCDI Connector" and use the same details you gave the partner manager. PointClickCare approves the account, then you verify your email and set up two-factor authentication. The instructions are under the portal's Documentation tab.

Step 3: register a development app

Under My Apps, create your first app. It must be a "Development" app. For each app you give:

• the app name users will see
• the app type: Patient, Provider or Bulk
• a description of what it does
• the authentication method and its details
• redirect and launch URLs
• the SMART scopes you need, in the exact format shown in the tool tip
• the Common Name of the certificate your app uses
• a communication email and the platform you build for

PointClickCare is firm on two of these. If the scopes are in the wrong format, "your App will not be able to access data". If the certificate Common Name is missing, "your application will not be approved". The list of supported certificates is in the portal's Documentation tab.

Development apps are approved automatically and enabled in the sandbox. Your client ID and secret appear under My Apps.

Step 4: register a production app

Production apps need PointClickCare's approval. The agreement adds an identity check: PointClickCare verifies your legal entity name and address with the relevant US Secretary of State "within ten (10) business days of the Developer submitting the Developed App to PointClickCare for publishing" (Terms and Conditions). Have your registered entity details ready and matching.

Step 5: get each facility enabled

This is the step that sets your launch date. Enablement "is driven by PCC customers, by Facility". The customer talks to their PointClickCare sales representative, and PointClickCare says enablement "will take a minimum of 2 weeks, depending on the number of Facilities where the enablement is requested and the complexity of their patient records" (FHIR API home). Under the agreement, the customer issues a Letter of Authorization for each facility before PointClickCare turns your app on there.

For a patient-facing app there is one more condition: the customer must also be enabled on Connected Care Center, PointClickCare's patient portal.

How PointClickCare API authentication works

PointClickCare says its "implementation of SMART on FHIR follows the public standard" and points to the SMART App Launch guide, May 2021 version (FHIR API home). The three app types map onto the usual SMART flows:

• Patient apps launch from Connected Care Center or a mobile device.
• Provider apps launch from inside the PointClickCare EHR or a mobile device, for users who have a PointClickCare account.
• Bulk apps are system-to-system and are never visible to users.

Access follows PointClickCare's own permissions: "Users (Patient or Provider) will only have access to patient records that their accounts are authorized to access in PointClickCare." PointClickCare tells customers to test how their access levels map to FHIR resources. If a nurse cannot see a resident in PointClickCare, your app will not see that resident through her token either.

What the discovery document says

The documentation does not list the OAuth URLs. The SMART discovery document does. We fetched /.well-known/smart-configuration for one organization from PointClickCare's endpoint list on 28 October 2026 (our own check, read-only, no credentials). It returned:

The advertised scope list is short. It does not show user/ or system/ scopes, though the capabilities list permission-user and client_credentials. Treat the scope list in the portal tool tip as the authority, and test your exact scope string in the sandbox before you build on it.

The client certificate

The registration form asks for the Common Name of your app's certificate, and approval depends on it. When we called the documented base host, connect2.pointclickcare.com, without a client certificate, it refused with "400 No required SSL certificate was sent" (our check, 28 October 2026). The other host, connect.pointclickcare.com, answered the same metadata request without one. Our reading is that API calls on connect2 need mutual TLS with the certificate you registered. PointClickCare's public pages do not say this in plain words, so confirm it in the portal documentation.

The agreement also says your app must not "store any plain text PointClickCare authorization credentials". Keep client secrets, private keys and refresh tokens in a secrets manager.

Endpoints and tenant IDs

Every FHIR call carries a tenant ID in the path. PointClickCare's example is https://connect2.pointclickcare.com/fhir/R4/{tenantId}/CareTeam.

The published endpoint list at R4endpoints.json is a FHIR Bundle of Endpoint and Organization resources. On 28 October 2026 it held 4,066 Endpoint entries, each paired with an Organization that has a name and street address (our count of the file). All 4,066 endpoint addresses in the file use the connect.pointclickcare.com host, while the documentation and the API specification name connect2.pointclickcare.com. Build your configuration so the host is a setting and confirm which one PointClickCare wants you to use in production.

The list is public, but an endpoint being listed does not mean the facility has enabled your app. Enablement still goes through the customer.

FHIR resources you can read

The API specification and the live CapabilityStatement agree on 26 resource types:

Every resource except Group supports read and search only. The specification lists these error codes: 400, 401, 403, 404, 405, 409, 410, 412, 422, 500 and 501. It does not list 429.

Patient search accepts identifier, given, family, name, birthdate, gender, general-practitioner, organization and _id.

One mismatch to know about. The FHIR home page points to US Core 3.1.1 and USCDI v1. The live CapabilityStatement we read on 28 October 2026 declares both US Core 3.1.1 and US Core 6.1.0, and names Smile CDR as the server ("FHIR Endpoint powered by Smile CDR"). Test whether your tenant returns 6.1.0 profiles before you depend on them.

Getting a CCD

PointClickCare documents how to fetch a Continuity of Care Document through DocumentReference (FHIR API home):

1. Search DocumentReference with the patient and type set to the CCD LOINC code given in the specification.
2. For the current CCD, you get one DocumentReference with one attachment. DocumentReference.content.attachment.url is the link that generates it.
3. For a date range, add period. You get one DocumentReference with a list of attachments, one per CCD.
4. Follow the URL. The CCD comes back as XML.

If a date-range search returns nothing, PointClickCare generates the current CCD on the fly. You need a Patient or Provider app for this; it is not listed for Bulk apps.

Bulk data export

Bulk apps use the FHIR Bulk Data standard. The specification has POST /{tenantId}/Group to create a group, GET or POST /{tenantId}/Group/{id}/$export to start an export, and /{tenantId}/$export-poll-status to check progress. The $export operation accepts _outputFormat, _type, _since, _until and _typeFilter, plus a few server-specific parameters (_typePostFetchFilterUrl, _exportId, _includeHistory, _mdm).

Use _since for nightly incremental pulls. Without webhooks, a scheduled bulk export or a scheduled search is how a USCDI Connector app finds out what changed.

PointClickCare sandbox

PointClickCare provides "a shared Sandbox for FHIR Apps to be tested against". Sandbox details are under My Sandboxes in the developer portal. For patient apps, use the test credentials that begin with ConnecterCareCenterUser (PointClickCare's spelling). For provider apps, use the ones that begin with vendortest.

Because the sandbox is shared, other developers use the same test data. Do not build tests that expect a fixed record count, and do not rely on data you created staying unchanged. Production facilities also configure PointClickCare differently from each other, so a sandbox pass is not proof that a given facility's data will map the same way.

PointClickCare API rate limits

PointClickCare does not publish a numeric rate limit for the USCDI Connector. The agreement says PointClickCare "may restrict the amount of data returned by certain queries to a specific page size or data set" and expects you to page through results. It also says PointClickCare may "suspend, throttle or otherwise limit" an app it believes threatens system stability or security (Terms and Conditions).

In practice: follow next links on every search, back off on 5xx responses, use bulk export for population pulls, and keep request volume per facility in your logs so you can answer PointClickCare if it asks. We did not load-test production and cannot give a number.

What can you write back to PointClickCare?

Through the USCDI Connector, nothing clinical. The published specification allows create on Group and nothing else. If your product needs to file a progress note, record an assessment, send an admission or update a resident, that is a Marketplace partner capability using proprietary APIs. The Marketplace listings and the eClinicalWorks announcement cited above show partners doing these writes. The exact write endpoints, validation rules and confirmation behaviour are in the partner documentation, which is not public.

When you design write-back, name the system that owns each result. Decide what happens when PointClickCare rejects a write, and who on the facility side sees the failure.

Real-time data: webhooks, polling and HL7

The comparison table lists "Real-time notification of data changes (webhooks)" for Marketplace partners only. The USCDI Connector CapabilityStatement has no Subscription resource. A USCDI Connector app has to poll, by search or by bulk export with _since.

PointClickCare's public pages do not publish HL7 v2 interface specifications. The Marketplace has a "Network Partners" section for connections to "Labs and Imaging Providers, Pharmacies, and HIEs" (Marketplace home). If your product is a lab, pharmacy or HIE that expects HL7 v2 feeds, raise it in the partnership conversation. We could not confirm message types or versions from public sources.

PointClickCare and Redox announced a partnership in March 2018 so health systems could exchange post-acute patient information with PointClickCare through the Redox platform (PointClickCare press release). The release does not describe the current scope, so check with both companies before you count on it.

How much does the PointClickCare API cost?

There are three separate costs.

First, the developer pays nothing for access. The agreement says PointClickCare makes the USCDI Connector APIs "available to Developer free of charge". The developer site also says "no upfront integration fees" (Developer Program).

Second, usage fees fall on the customer. The FHIR site's pricing section says: "Customers under PCC's current pricing model will be charged a flat fee of $65 per App per Facility per Month. This price will be subject to annual revision, in line with costs incurred by PointClickCare." The agreement says usage-based fees may apply to activated customers or to a health system or provider, under a separate written agreement. A product used at 40 facilities would cost those customers 40 × $65 = $2,600 a month at the published rate. That figure is our own arithmetic on the published rate. Customers on other pricing models may pay something else, and PointClickCare does not publish those terms.

Third, Marketplace partner fees. We found no public figure. Ask the partner manager in the first call, and ask whether the $65 per facility fee also applies to Marketplace apps.

PointClickCare's certification costs page lists costs for e-prescribing, data migration and exchange networks. It does not list an API cost. Your own build effort is separate from all of these.

Contract terms that change your design

The USCDI Connector API Access Agreement (tc.html) has terms that belong in your architecture document:

• The app must not be accessed or supported "from outside of Canada or the United States of America". This affects where you host, where support staff log in from, and whether an offshore team can touch production.
• No plain-text storage of PointClickCare credentials.
• No robots, crawlers or screen scraping against the APIs or PointClickCare products, including for monitoring or benchmarking.
• You must handle audit requests from activated customers, "including with respect to logging, reporting of statistics, and third-party security assessments".
• The app must handle EHR events such as patient context and user context changes, and must handle changes to the underlying data.
• PointClickCare posts API updates on its website, and keeping your app compatible is your job.
• Either side can end the agreement on 60 days' written notice. Termination for cause needs 30 days' notice of an uncured breach.
• The agreement says the developer is not a downstream business associate of PointClickCare under HIPAA for this access. Your HIPAA duties to your own customers still apply.

Marketplace partners sign a separate agreement that is not public.

What about scraping or the reporting database?

Some integrations still use screen scraping or copies of a reporting database. The USCDI Connector agreement prohibits automated scraping of PointClickCare products by API developers. PointClickCare's position is that vendors must use authorized channels.

There is also a court case. Real Time Medical Systems sued PointClickCare after PointClickCare blocked its automated access to customer data. The Fourth Circuit upheld a preliminary injunction against PointClickCare in March 2025 and denied rehearing en banc in April 2025, and the case went back to the district court (Sequoia Project case summary; case analysis on cmhealthlaw.com). A preliminary injunction is not a final ruling, and we did not check the case status after remand. Talk to your own counsel before you build anything other than the authorized programs. We cover the hospital side of this in our Epic integration guide for skilled nursing facilities.

Certification: what PointClickCare's ONC listing covers

PointClickCare's certifications page lists § 170.315(g)(10), the standardized API criterion, and (b)(10) EHI export. The certified product named there is "EHR for Practice Groups" (2025 entry: version v3, certified 8 December 2025, certification number 15.04.04.2181.Poin.03.01.1.251208). The core skilled nursing EHR is listed on that page only as supporting software. If your buyer asks whether the API they will use is certified, look up the listing on CHPL with them.

Common problems and how to fix them

These come from PointClickCare's documentation and from our own read-only checks on 28 October 2026. We have not run a production integration against these hosts.

How long does a PointClickCare integration take?

PointClickCare publishes two durations: up to 10 business days for the developer identity check, and at least 2 weeks per enablement request. It does not publish how long partnership review, production app approval or Marketplace technical validation take.

For a read-only USCDI Connector app, the build itself is a normal SMART on FHIR project. The calendar time usually goes to the partnership conversation and to each customer's enablement. For a Marketplace integration with write-back, add the partner agreement and PointClickCare's technical validation. We have no public basis for a number on either, and we would rather you ask PointClickCare than plan on a guess.

PointClickCare API checklist

1. Write down every read and write your product needs, and whether it needs to happen in real time.
2. Mark which of those the USCDI Connector covers. Anything else points to the Marketplace.
3. Check where your app will be hosted and supported from against the US or Canada clause.
4. Submit the partnership form with the same legal entity details you will use later.
5. Get a client certificate PointClickCare supports, and record its Common Name.
6. Build against the shared sandbox with the vendortest or ConnecterCareCenterUser accounts.
7. Make the FHIR host and tenant ID configurable settings.
8. Page every search and use bulk export with _since for population data.
9. Store secrets in a secrets manager. Log request volume per facility.
10. Agree with each customer who will request enablement and sign the Letter of Authorization, and budget the $65 per facility per month on their side.
11. Test each facility's data before you call it live. Configurations differ.

Getting help with a PointClickCare integration

Nirmitee is an engineering team that builds healthcare integrations, including SMART on FHIR apps, bulk data pipelines and HL7 interfaces. We are not a PointClickCare Marketplace partner and cannot get you a listing; that decision sits between your company and PointClickCare. We can help you choose the route, prepare the application details, build and test the integration and plan facility rollout. See PointClickCare integration services to scope a project. For the standards underneath, our guides on SMART on FHIR authorization and USCDI v3 data elements go deeper.

Sources (all read 28 October 2026)

• PointClickCare FHIR API home (USCDI Connector, registration, enablement, sandbox, CCD, pricing): https://fhir.pointclickcare.com/
• PointClickCare FHIR API specification: https://fhir.pointclickcare.com/PointClickCare.html
• PointClickCare USCDI Connector API Access Agreement: https://fhir.pointclickcare.com/tc.html
• PointClickCare service base URL list: https://fhir.pointclickcare.com/R4endpoints.json
• PointClickCare SMART configuration and CapabilityStatement (one public tenant, read-only): https://connect.pointclickcare.com/fhir/R4/{tenantId}/.well-known/smart-configuration and /metadata
• PointClickCare Developer Program home: https://developer.pointclickcare.com/
• PointClickCare Developer Program comparison table: https://developer.pointclickcare.com/spa/why-pcc
• PointClickCare Marketplace home: https://marketplace.pointclickcare.com/home
• PointClickCare partnership inquiry form: https://marketplace.pointclickcare.com/s/data-access-and-partnership-inquiries
• PointClickCare certifications: https://pointclickcare.com/company/certifications/
• PointClickCare certification costs: https://pointclickcare.com/company/certifications/costs/
• PointClickCare and Redox press release (6 March 2018): https://pointclickcare.com/press-releases/product-news/pointclickcare-redox-strategic-partnership/
• eClinicalWorks Marketplace press release (3 March 2025): https://www.eclinicalworks.com/eclinicalworks-launches-integrated-solution-on-pointclickcare-marketplace-to-streamline-data-exchange-with-skilled-nursing-facilities/
• Sequoia Project, Real Time Medical Systems v. PointClickCare: https://sequoiaproject.org/cases-and-laws/real-time-medical-systems-inc-v-pointclickcare-technologies-inc-d-b-a-pointclickcare/
• Case analysis, cmhealthlaw.com (May 2025): https://www.cmhealthlaw.com/2025/05/recent-federal-cases-on-information-blocking-violations-pave-way-for-state-court-claims-and-shed-light-on-manner-exception/

Planning an integration like this one? Our healthcare interoperability team builds and supports vendor API, FHIR and HL7 integrations for product companies. Talk to our team to scope yours.