Secrets fields (marked
isSecret in templates) are write-only. Once saved, they cannot be retrieved by any GET endpoint. To replace a secret, use the rotate-secrets endpoint.Integration types
TheintegrationType field uses the following enumeration values:
| Value | Description |
|---|---|
1 | Payment |
2 | Accounting |
3 | Shipping |
4 | |
5 | Sms |
6 | Analytics |
7 | Crm |
8 | Inventory |
GET /api/integration-templates
Returns all available integration templates. Use templates to understand which fields are required before creating an integration. For OAuth providers (e.g. QuickBooks), the response includes thecallbackUrl you must register with the external service.
Security: Admin policy
Query parameters
Filter templates by integration type. See the Integration types table for valid values. Omit to return all templates.
Response
Array of integration template objects.
Example response
curl example — all templates
curl example — filter by type
GET /api/integrations/available
Returns all available integration templates enriched with the current configuration and connection status for your organization. Results are grouped by integration type. Security: Admin policyResponse
Your organization’s identifier.
Total number of available integrations.
Number of integrations you have configured.
Number of integrations that are currently enabled.
Dictionary keyed by integration type, where each value is an array of
AvailableIntegration objects.curl example
POST /api/organizations//integrations
Creates a new integration for the specified organization. Pass non-sensitive settings inconfiguration and sensitive credentials in secrets — secrets are encrypted at rest and are never returned by any GET endpoint.
Security: Admin policy
Path parameters
Your organization’s unique identifier.
Request body
Integration type. See the Integration types table.
Provider identifier, e.g.
AuthorizeNet or QuickBooks. Must match a template provider value.A human-readable name for this integration instance (e.g.
Main Payment Gateway).Whether the integration should be enabled immediately.
Key-value pairs of non-sensitive configuration settings. Keys must match the
configurationFields keys from the provider’s template.Key-value pairs of sensitive credentials. Keys must match the
secretFields keys from the provider’s template. Values are stored encrypted and are never returned.Response
Unique identifier of the newly created integration.
Your organization’s identifier.
Integration type.
Provider identifier.
Display name of the integration.
Whether the integration is enabled.
ISO 8601 timestamp of when the integration was created.
Example request — Authorize.Net
Example response
curl example
GET /api/organizations//integrations
Returns all integrations configured for the specified organization. Secrets are never included in the response. Security: Admin policyPath parameters
Your organization’s unique identifier.
Query parameters
Filter results by integration type. See the Integration types table.
Filter results by enabled status. Omit to return all.
Response
Array of integration summary objects (secrets omitted).
curl example
GET /api/organizations//integrations/
Returns detailed information about a specific integration, including its configuration and the list of available fields from the provider template. Secrets are never included. Security: Admin policyPath parameters
Your organization’s unique identifier.
The integration’s unique identifier.
Response
Unique integration identifier.
Organization identifier.
Integration type.
Provider identifier.
Display name.
Whether the integration is enabled.
ISO 8601 creation timestamp.
ISO 8601 last-updated timestamp.
Non-sensitive configuration key-value pairs. Secrets are excluded.
Identity of the user who created the integration.
Fields available for this provider from the template, including
configurationFields, secretFields, requiresOAuth, documentationUrl, and supportedFeatures.curl example
PUT /api/organizations//integrations/
Updates an existing integration’s display name, enabled status, configuration, and/or secrets. If you update secrets, the API flags that a connection test is recommended. Security: Admin policyPath parameters
Your organization’s unique identifier.
The integration’s unique identifier.
Request body
New display name for the integration.
Enable or disable the integration.
Updated non-sensitive configuration key-value pairs. Merged with existing configuration.
Updated secret key-value pairs. Values are encrypted and overwrite existing secrets for the supplied keys. Cannot be retrieved after saving.
Response
true if secrets or critical configuration keys (e.g. IsSandbox, Environment) were changed. Run a connection test to verify.curl example
POST /api/organizations//integrations//test
Tests connectivity and authentication for the specified integration. The result is recorded on the integration and reflected in thetestStatus field of subsequent list/get responses.
Security: Admin policy
Path parameters
Your organization’s unique identifier.
The integration’s unique identifier.
Response
The integration that was tested.
true if the connection test passed.Human-readable result message (e.g.
Connection test successful).ISO 8601 timestamp of when the test was performed.
Example response
curl example
POST /api/organizations//integrations//connect
Initiates an OAuth authorization flow for OAuth-based providers (e.g. QuickBooks). Returns anauthorizationUrl that you redirect the user to. The OAuth URL expires after 15 minutes.
Security: Admin policy
Path parameters
Your organization’s unique identifier. Resolved from the JWT
OrganizationId claim.The integration’s unique identifier.
Request body
An opaque string (typically your application’s return URL) that Nymble Commerce encodes into the OAuth state parameter and returns to your callback. Use this to redirect the user back to the correct page after authorization.
Response
The OAuth authorization URL. Redirect your user to this URL to begin the OAuth flow.
curl example
POST /api/organizations//integrations//rotate-secrets
Rotates (replaces) the secrets for the specified integration. Optionally runs a connection test after rotation to validate the new credentials. Use this endpoint for periodic security compliance key rotation. Security: Admin policyPath parameters
Your organization’s unique identifier.
The integration’s unique identifier.
Request body
Key-value pairs of new secret values. Keys must match the
secretFields keys from the provider’s template. Values are encrypted at rest and are never returned.Whether to automatically run a connection test after updating the secrets. Strongly recommended.
Response
true if the post-rotation connection test passed. Only meaningful when testConnectionAfterRotation was true.Example request
Example response
curl example
DELETE /api/organizations//integrations/
Permanently deletes an integration and all associated configuration and encrypted credentials. Security: Admin policyPath parameters
Your organization’s unique identifier.
The integration’s unique identifier.
Response
curl example