Platform Connector: Integration Configurations (1.0.0)
Download OpenAPI specification:Download
This API allows authors of Platform Connectors to configure the integration between their Platform Connector and Bold services.
Refer to the changelog for the latest updates to this API.
Note: This specification is only for use with a Bold Platform Connector.
bearerAuth
The API access token created in Bold Account Center. For more information about creating an API Access token, refer to the Quick Start.
| Security Scheme Type | HTTP |
|---|---|
| HTTP Authorization Scheme | bearer |
These endpoints allow you to integrate a Platform Connector with Bold by providing your server's destinations.
Create Destination
Informs Bold of your platform connector destination for the specified shop_identifier. This destination is considered the location of your platform connector server.
Subsequently, any time the specified topic resource is changed, Bold makes a call to your platform connector's destination URL at the relevant path. For more information about implementing these paths, refer to Implement Platform Connector APIs.
Each topic may only have a single destination on the Platform Connector, and each destination corresponds to only one topic. You must make separate calls to register each destination.
Any request to this endpoint also results in a synchronous request to the Verify Platform Connector Destination endpoint on your platform connector. If the verification endpoint does not respond correctly the request change with not be completed and an error response will be returned.
Authorizations:
path Parameters
| shop_identifier required | string Unique identifier of the store. Retrieve this information by calling the Get Shop Info endpoint. |
Request Body schema: application/json
object (createDestinationRequestData) | |||||||||||||||
| |||||||||||||||
Responses
Request samples
- Payload
{- "data": {
- "destination": {
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
}
}Response samples
- 200
- 500
{- "data": {
- "destination": {
- "id": 100,
- "created_at": "2019-08-24T14:15:22Z",
- "updated_at": "2019-08-24T14:15:22Z",
- "deleted_at": "2019-08-24T14:15:22Z",
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
}
}List Destinations
Lists all connections between Bold and your Platform Connector for the specified shop_identifier.
These describe the expected calls any time the referenced topic resources are changed; your Platform Connector will be called on the specified destination base URL at the relevant path as per the Platform Connector specifications.
Authorizations:
path Parameters
| shop_identifier required | string Unique identifier of the store. Retrieve this information by calling the Get Shop Info endpoint. |
Responses
Response samples
- 200
- 500
{- "data": {
- "destinations": [
- {
- "id": 100,
- "created_at": "2019-08-24T14:15:22Z",
- "updated_at": "2019-08-24T14:15:22Z",
- "deleted_at": "2019-08-24T14:15:22Z",
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
]
}
}Get Destination by ID
Retrieves a specific connection between Bold and your Platform Connector for the specified shop_identifier by its unique id.
The response describes the expected calls any time the referenced topic resource is changed; Bold makes a call to your Platform Connector destination base URL at the relevant path.
Authorizations:
path Parameters
| shop_identifier required | string Unique identifier of the store. Retrieve this information by calling the Get Shop Info endpoint. |
| id required | string Unique identifier of the destination. |
Responses
Response samples
- 200
- 404
- 500
{- "data": {
- "destination": {
- "id": 100,
- "created_at": "2019-08-24T14:15:22Z",
- "updated_at": "2019-08-24T14:15:22Z",
- "deleted_at": "2019-08-24T14:15:22Z",
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
}
}Update Destination
Updates the base url destination of your Platform Connector for the specified shop_identifier.
All fields of a destination object are replaced with the values provided in the request body. Fields omitted from the request body are ignored in the Destination object.
Subsequently, any time the specified topic resource is changed, Bold makes a call to your platform connector's destination field at the relevant path. For more information about implementing these paths, refer to Implement Platform Connector APIs.
Each topic may only have a single destination on the Platform Connector, and each destination corresponds to only one topic. You must make separate calls to register each destination.
Any request to this endpoint also results in a synchronous request to the Verify Platform Connector Destination endpoint on your platform connector. If the verification endpoint does not respond correctly the request change with not be completed and an error response will be returned.
Authorizations:
path Parameters
| shop_identifier required | string Unique identifier of the store. Retrieve this information by calling the Get Shop Info endpoint. |
| id required | string Unique identifier of the destination. |
Request Body schema: application/json
object (updateDestinationRequestData) | |||||||||||||||||
| |||||||||||||||||
Responses
Request samples
- Payload
{- "data": {
- "destination": {
- "id": 100,
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
}
}Response samples
- 200
- 404
- 500
{- "data": {
- "destination": {
- "id": 100,
- "created_at": "2019-08-24T14:15:22Z",
- "updated_at": "2019-08-24T14:15:22Z",
- "deleted_at": "2019-08-24T14:15:22Z",
- "shop_identifier": "abc123xyz",
- "topic": "customers",
- "version": "v1",
- "timeout_ms": 10000
}
}
}Delete Destination
Deletes a specific connection between Bold and your Platform Connector for the specified shop_identifier by its unique id.
After this call, topic changes which would normally trigger calls to a Platform Connector will no longer do so for the deleted topic.
Authorizations:
path Parameters
| shop_identifier required | string Unique identifier of the store. Retrieve this information by calling the Get Shop Info endpoint. |
| id required | string Unique identifier of the destination. |
Responses
Response samples
- 204
- 404
- 500
{ }