Create organization external provider
Creates a new organization external provider. BadRequestError is returned when the NPI is already in use.
Authorization
BearerAuth Send your Taiga API key as a Bearer token. Create and manage keys in the Taiga developer portal.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
An object representing an organization-level external provider.
Response Body
application/json
application/json
curl -X POST "https://example.com/organization-external-providers/v1" \ -H "Content-Type: application/json" \ -d '{ "name": { "family": "string", "given": [ "string" ], "use": "USUAL" }, "types": [ "REFERRING" ] }'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "organization_id": "string", "deactivated": true, "version": 0, "updated_at": "2019-08-24T14:15:22Z", "updating_user_id": "string", "name": { "family": "string", "given": [ "string" ], "use": "USUAL", "period": { "start": "2019-08-24", "end": "2019-08-24" }, "suffix": "string" }, "types": [ "REFERRING" ], "npi": "string", "tax_id": "string", "taxonomy_code": "string", "phone_number": "string", "other_phone_numbers": [ "string" ], "fax_number": "string", "other_fax_numbers": [ "string" ], "emails": [ "string" ], "license_type": "MD", "addresses": [ { "use": "HOME", "line": [ "string" ], "city": "string", "state": "string", "postal_code": "string", "country": "string", "county": "string", "period": { "start": "2019-08-24", "end": "2019-08-24" } } ]}List organization external providers GET
Searches for organization external providers that match the query parameters.
Scan organization external provider updates GET
Scans up to 1000 organization external provider updates. The since query parameter is inclusive, and the result list is ordered by updatedAt ascending. **Polling Pattern:** To continuously poll for updates without gaps: 1. Make your initial request with a `since` timestamp (e.g., `since=2020-01-01T13:00:00.000Z`) 2. The API returns 100 by default and up to 1000 records, sorted by `updated_at` ascending 3. Find the `updated_at` value from the last record in the response 4. Use that `updated_at` value as the `since` parameter in your next request 5. Repeat steps 2-4 to ingest updates until you receive an empty list **Important Notes:** - The `since` parameter is inclusive, so you may receive the last record from the previous batch again (you can deduplicate by ID and version) - All records include `updated_at`, `id`, `version`, `deactivated`, and `updating_user` fields for tracking changes - Timestamps have millisecond resolution for precise ordering