openapi: 3.1.0
info:
title: Channable order connection order_attachments API
description: "# Introduction\n\nWelcome to the Channable API __v1__.\n\nThis version of the Channable API allows you to:\n\n- Access orders\n- Manage order shipments\n- Update the stock of an offer on all marketplaces\n- Access returns\n\n### Details\n\n| Key | Value\n------------- | -----------\nApi version | `v1`, `v2`\nProtocol | `HTTPS`\nHostname | `api.channable.com`\nCommon Path v1 | `/v1/companies/:company_id/projects/:project_id`\nCommon Path v2 | `/v2/companies/:company_id/projects/:project_id`\n\n\nThe Common Path is shared by all endpoints except the transporters endpoints in this version of our API. Note that you have to replace :company_id and :project_id with valid values. All endpoints using v2 will state so in their names, and should use the common path v2. All other endpoints are v1 endpoints and should use Common Path v1.\n\n## Taxonomy\n\n\n| Term | Description\n------------- | -----------\n`Platform` | A webshop platform, such as WooComerce, Lightspeed, etc.\n`Marketplace` | A place where you can sell your products, such as Amazon, Bol, eBay, etc. Sometimes referred to as _channel_.\n`Order` | A purchase of any products made by a client.\n`Offer` | A selling proposal made by a seller over any class of products. It includes price, stock and other seller-dependent values.\n\n\n## Rate Limiting\n\nThe Channable API has a rate limiting policy to which you must comply. \nIt is defined on a per-company basis, meaning that generating new API tokens will not circumvent our rate-limiting.\n\n| Frequency | Burst\n------------- | -----------\nMax 4 requests per second | Burst of 200 requests\n\n**Note**: We use the [Leaky Bucket algorithm](https://en.wikipedia.org/wiki/Leaky_bucket) for rate-limiting.\n\n## Getting started\n\n\nTo get started you need to:\n\n1. Find the project ids you are interested in\n1. Find your Channable company id\n1. Generate an **API token** for your company\n\n**Note**: Information about the supported channels can be found in our [help center](https://helpcenter.channable.com/hc/en-us/articles/360011094300-For-which-marketplaces-does-Channable-support-an-order-connection-integration-).\n\n### 1. Find your project ids\n\nTo find the project ids you are interested in:\n\n1. Log in to the Channable app\n2. Select a project\n3. Open the project `Settings`\n4. Copy the _Project id_ value\n\n\n### 2. Generate an API Token for your company\n\nTo both find your Channable `company_id` and to generate a new **API token** for your company, go to [app.channable.com](https://app.channable.com) and sign in.\n\nOn the main page navigate to company settings then channabke API.\nFrom here you can see your company id, as well as generate your API token.\n\n\n\n**Notes**:\n\n- Only owners of companies are able to generate an API Token.\n- Channable does not store your tokens. Please store them securely.\n- In case you lose or leak your token, generate a new one. The previously generated tokens can be revoked by you or will expire after 1 year.\n- Two API tokens can be valid at any time, allowing you to seamlessly change to a new token, if needed.\n\n### 3. Using the API Token\n\nYou must include your API token in every request you make to Channable. \nThe token should be included in the headers of the request: `Authorization: Bearer your_api_token`\n\n\n\nAfter generating your API token you are ready to try out the endpoints and build your integration\nusing the Channable Sandbox.\n\n**How to include the token in your requests:**\n\n```shell\n# Headers method: Authorization: Bearer\ncurl \"api_endpoint_here\"\n -H \"Authorization: Bearer your_api_token\"\n```\n\n\n### Common error codes and their meanings\n\nThe Channable API uses the following error codes:\n\nCode | Meaning | Reason\n---------- | ------- | -------\n400 | Bad Request | The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)\n401 | Unauthorized | You are using an invalid or already revoked API token.\n403 | Forbidden | You are not allowed to access the resources your request targets.\n404 | Not Found | The targeted resources could not be found.\n405 | Method Not Allowed | You tried to access an endpoint with an invalid HTTP method.\n406 | Not Acceptable | You requested a format that isn't json.\n409 | Conflict | Your request could not be completed due to a conflict with the current state of the target resource.\n422 | Unprocessable Entity | We could understand the content type of the request entity, but we are unable to process the contained instructions.\n429 | Too Many Requests | You have sent too many requests in a given amount of time, thus exceeding our rate-limiting policy. Please try again later.\n500 | Internal Server Error | We had a problem with our server. Please try again later.\n503 | Service Unavailable | We are temporarily offline for maintenance. Please try again later.\n\n\n## Sandbox Testing\n\nThe Channable API sandbox lets you test your order integration with the Channable API in a safe\nenvironment without sending requests to the marketplaces you want to connect to. All data is mocked\nbut the structure of the data and API calls needed to manage your orders are the same no matter\nwhich marketplace you end up connecting with.\n\n\n### Setup\n\nTo set up a test environment with the Channable Sandbox you must first make a connection with the\nSandbox. This can be done in the same way as all other connections within Channable by going to\n\"Company settings\" -> \"Connections\" and clicking on \"+ Add new connection\".\n\n\n\nSelect \"Channable Sandbox\", give the connection a label and click on the blue \"Create\" button.\nNo further information is needed.\n\nOnce you have made a connection, navigate to the project you want to use and click on\n\"Setup\" -> \"Setup orders\" > \"+ Setup orders\".\n\n\n\nFrom here make an order connection between the \"Channable API\" and the \"Channable Sandbox\" and\nactivate the order connection. You are now ready to start testing.\n\n\n\n### Orders\n\nTo create a test order, navigate to \"Setup\" -> \"Orders\" -> \"Settings\" of the Channable Sandbox\norder connection.\n\n\n\nFrom here click on the gear in the top right and \"Send test order\".\n\n\n\nIn the popup fill in an item id and click the blue \"Send test order\" button. A test order has now\nbeen created, and you can use all request methods described in \"Orders\" to interact with it. If you\nneed special test cases, most data in the test order can be provided by you in the popup when you\nclick on \"Send test order\".\n\n\n### Shipments/Cancellations\n\nOnce one or more testorders have been created, use the request methods described in \"Shipment\nupdate\" and \"Cancellation update\" under \"Orders\" above to mark an order as \"shipped\" and to give it\ntrack & trace information or to mark the order as \"cancelled\".\n\n\n### Offers\n\nTo test sending offer updates, that is updating the stock value on all marketplaces that you have\nan order connection to, you can use the request methods described in \"Offers\" above. You do not need\nto have created a test order to test this as you can update the stock value of any product in your\nstore, also products that you have not received an order for through Channable.\n\n\n### Returns\n\nReturns come from the marketplaces you will connect to. In order to test this, navigate to\n\"Setup\" -> \"Setup orders\" -> \"Settings\" of the Channable Sandbox order connection. \n\n\n\nFrom here click on the gear in the top right and \"Send test return\".\n\n\n\nIn the popup fill in a Channable order id and click the blue \"Send test return\" button. A test\nreturn has now been created for the order id you filled in. You can now use all request methods\ndescribed in \"Returns\" to handle the return.\n\n\n### When you are done testing\n\nOnce you are satisfied with your Channable API setup and want to go live, contact our\nsupport department\nand they will help you setup the order connections.\n"
version: v1
x-logo:
url: https://www.channable.com/_next/image?url=https%3A%2F%2Fmedia.graphassets.com%2FcntRnbAcSrCmS1wLTWrb&w=256&q=75
tags:
- name: order_attachments
paths:
/v1/companies/{company_id}/projects/{project_id}/orders/{order_id}/attachments/{order_attachment_id}:
get:
tags:
- order_attachments
summary: Order attachment download
description: 'This endpoint responds with the download URL for an order attachment.
The download URL is valid for 5 minutes.'
operationId: order_attachment_download_url_companies__company_id__projects__project_id__orders__order_id__attachments__order_attachment_id__get
parameters:
- name: company_id
in: path
required: true
schema:
type: integer
title: Company Id
- name: project_id
in: path
required: true
schema:
type: integer
title: Project Id
- name: order_id
in: path
required: true
schema:
type: integer
description: The order ID as it is known to Channable
title: Order Id
description: The order ID as it is known to Channable
- name: order_attachment_id
in: path
required: true
schema:
type: integer
title: Order Attachment Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentDownloadURLResponse'
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Not Found
'410':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Gone
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/v1/companies/{company_id}/projects/{project_id}/orders/{order_id}/attachments:
post:
tags:
- order_attachments
summary: Order attachment upload
description: "Order attachments sent to this endpoint will be uploaded to the marketplace and linked to the specified order (items). A 202 status response indicates the file has been processed and will be uploaded asynchronously.\n\nCurrently only accepts PDF invoices.\n\nAvailable for:\n - ANWB\n- Allegro\n- Amazon\n- Bol\n- Boulanger\n- But\n- Carrefour\n- Carrefour France\n- Castorama\n- Channable Sandbox\n- Conforama\n- Conrad\n- Debenhams\n- Decathlon\n- Douglas\n- Galeries LaFayette\n- Home24\n- Hornbach\n- Inno\n- Kaufland\n- Kruidvat\n- La Redoute\n- Le BHV Marais\n- Leen Bakker\n- Leroy Merlin\n- Maisons Du Monde\n- Manor\n- Maxeda Brico\n- Maxeda Praxis\n- MediaMarkt\n- Nextail\n- Nocibe\n- Obelink\n- Pc Componentes\n- Shop Apotheke Austria\n- Shop Apotheke Belgium\n- Shop Apotheke Germany\n- Shop Apotheke Italy\n- Showroomprive\n- Sprinter\n- Teract\n- Worten\n- ePrice\n- fonQ\n- vtwonen"
operationId: order_attachment_upload_companies__company_id__projects__project_id__orders__order_id__attachments_post
parameters:
- name: company_id
in: path
required: true
schema:
type: integer
title: Company Id
- name: project_id
in: path
required: true
schema:
type: integer
title: Project Id
- name: order_id
in: path
required: true
schema:
type: integer
description: The order ID as it is known to Channable
title: Order Id
description: The order ID as it is known to Channable
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentUploadPayload'
responses:
'202':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentUploadResponse'
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Bad Request
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Not Found
'409':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Conflict
'415':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Unsupported Media Type
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
OrderAttachmentDownloadURLResponse:
properties:
url:
type: string
title: Url
type: object
required:
- url
title: OrderAttachmentDownloadURLResponse
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
OrderAttachmentUploadPayload:
properties:
attachment_type:
type: string
title: Attachment Type
description: Only `INVOICE` is currently accepted
default: INVOICE
file:
type: string
title: File
description: A base64 encoded string
order_item_ids:
anyOf:
- items:
type: integer
type: array
- type: 'null'
title: Order Item Ids
description: Only used for Bol invoices. Order item ids of the subset of items the invoiceis for. If omitted the invoice will be linked to all items in the order.
type: object
required:
- file
title: OrderAttachmentUploadPayload
ChannableErrorResponse:
properties:
status:
type: string
const: error
title: Status
default: error
message:
type: string
title: Message
description: A description about the given error
type: object
required:
- message
title: ChannableErrorResponse
description: The standard Channable error response
OrderAttachmentUploadResponse:
properties:
status:
$ref: '#/components/schemas/ResponseModelStatus'
order_attachment_id:
anyOf:
- type: integer
- type: 'null'
title: Order Attachment Id
description: Channable ID for the attachment. Is empty on failure
message:
anyOf:
- type: string
- type: 'null'
title: Message
type: object
required:
- status
title: OrderAttachmentUploadResponse
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ResponseModelStatus:
type: string
enum:
- success
- error
- warning
- debug
title: ResponseModelStatus
\n\n**Notes**:\n\n- Only owners of companies are able to generate an API Token.\n- Channable does not store your tokens. Please store them securely.\n- In case you lose or leak your token, generate a new one. The previously generated tokens can be revoked by you or will expire after 1 year.\n- Two API tokens can be valid at any time, allowing you to seamlessly change to a new token, if needed.\n\n### 3. Using the API Token\n\nYou must include your API token in every request you make to Channable.
\n\nSelect \"Channable Sandbox\", give the connection a label and click on the blue \"Create\" button.\nNo further information is needed.\n\nOnce you have made a connection, navigate to the project you want to use and click on\n\"Setup\" -> \"Setup orders\" > \"+ Setup orders\".\n\n
\n\nFrom here make an order connection between the \"Channable API\" and the \"Channable Sandbox\" and\nactivate the order connection. You are now ready to start testing.\n\n
\n\n### Orders\n\nTo create a test order, navigate to \"Setup\" -> \"Orders\" -> \"Settings\" of the Channable Sandbox\norder connection.\n\n
\n\nFrom here click on the gear in the top right and \"Send test order\".\n\n
\n\nIn the popup fill in an item id and click the blue \"Send test order\" button. A test order has now\nbeen created, and you can use all request methods described in \"Orders\" to interact with it. If you\nneed special test cases, most data in the test order can be provided by you in the popup when you\nclick on \"Send test order\".\n\n\n### Shipments/Cancellations\n\nOnce one or more testorders have been created, use the request methods described in \"Shipment\nupdate\" and \"Cancellation update\" under \"Orders\" above to mark an order as \"shipped\" and to give it\ntrack & trace information or to mark the order as \"cancelled\".\n\n\n### Offers\n\nTo test sending offer updates, that is updating the stock value on all marketplaces that you have\nan order connection to, you can use the request methods described in \"Offers\" above. You do not need\nto have created a test order to test this as you can update the stock value of any product in your\nstore, also products that you have not received an order for through Channable.\n\n\n### Returns\n\nReturns come from the marketplaces you will connect to. In order to test this, navigate to\n\"Setup\" -> \"Setup orders\" -> \"Settings\" of the Channable Sandbox order connection. \n\n
\n\nIn the popup fill in a Channable order id and click the blue \"Send test return\" button. A test\nreturn has now been created for the order id you filled in. You can now use all request methods\ndescribed in \"Returns\" to handle the return.\n\n\n### When you are done testing\n\nOnce you are satisfied with your Channable API setup and want to go live, contact our\nsupport department\nand they will help you setup the order connections.\n"
version: v1
x-logo:
url: https://www.channable.com/_next/image?url=https%3A%2F%2Fmedia.graphassets.com%2FcntRnbAcSrCmS1wLTWrb&w=256&q=75
tags:
- name: order_attachments
paths:
/v1/companies/{company_id}/projects/{project_id}/orders/{order_id}/attachments/{order_attachment_id}:
get:
tags:
- order_attachments
summary: Order attachment download
description: 'This endpoint responds with the download URL for an order attachment.
The download URL is valid for 5 minutes.'
operationId: order_attachment_download_url_companies__company_id__projects__project_id__orders__order_id__attachments__order_attachment_id__get
parameters:
- name: company_id
in: path
required: true
schema:
type: integer
title: Company Id
- name: project_id
in: path
required: true
schema:
type: integer
title: Project Id
- name: order_id
in: path
required: true
schema:
type: integer
description: The order ID as it is known to Channable
title: Order Id
description: The order ID as it is known to Channable
- name: order_attachment_id
in: path
required: true
schema:
type: integer
title: Order Attachment Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentDownloadURLResponse'
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Not Found
'410':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Gone
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/v1/companies/{company_id}/projects/{project_id}/orders/{order_id}/attachments:
post:
tags:
- order_attachments
summary: Order attachment upload
description: "Order attachments sent to this endpoint will be uploaded to the marketplace and linked to the specified order (items). A 202 status response indicates the file has been processed and will be uploaded asynchronously.\n\nCurrently only accepts PDF invoices.\n\nAvailable for:\n - ANWB\n- Allegro\n- Amazon\n- Bol\n- Boulanger\n- But\n- Carrefour\n- Carrefour France\n- Castorama\n- Channable Sandbox\n- Conforama\n- Conrad\n- Debenhams\n- Decathlon\n- Douglas\n- Galeries LaFayette\n- Home24\n- Hornbach\n- Inno\n- Kaufland\n- Kruidvat\n- La Redoute\n- Le BHV Marais\n- Leen Bakker\n- Leroy Merlin\n- Maisons Du Monde\n- Manor\n- Maxeda Brico\n- Maxeda Praxis\n- MediaMarkt\n- Nextail\n- Nocibe\n- Obelink\n- Pc Componentes\n- Shop Apotheke Austria\n- Shop Apotheke Belgium\n- Shop Apotheke Germany\n- Shop Apotheke Italy\n- Showroomprive\n- Sprinter\n- Teract\n- Worten\n- ePrice\n- fonQ\n- vtwonen"
operationId: order_attachment_upload_companies__company_id__projects__project_id__orders__order_id__attachments_post
parameters:
- name: company_id
in: path
required: true
schema:
type: integer
title: Company Id
- name: project_id
in: path
required: true
schema:
type: integer
title: Project Id
- name: order_id
in: path
required: true
schema:
type: integer
description: The order ID as it is known to Channable
title: Order Id
description: The order ID as it is known to Channable
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentUploadPayload'
responses:
'202':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/OrderAttachmentUploadResponse'
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Bad Request
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Not Found
'409':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Conflict
'415':
content:
application/json:
schema:
$ref: '#/components/schemas/ChannableErrorResponse'
description: Unsupported Media Type
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
OrderAttachmentDownloadURLResponse:
properties:
url:
type: string
title: Url
type: object
required:
- url
title: OrderAttachmentDownloadURLResponse
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
OrderAttachmentUploadPayload:
properties:
attachment_type:
type: string
title: Attachment Type
description: Only `INVOICE` is currently accepted
default: INVOICE
file:
type: string
title: File
description: A base64 encoded string
order_item_ids:
anyOf:
- items:
type: integer
type: array
- type: 'null'
title: Order Item Ids
description: Only used for Bol invoices. Order item ids of the subset of items the invoiceis for. If omitted the invoice will be linked to all items in the order.
type: object
required:
- file
title: OrderAttachmentUploadPayload
ChannableErrorResponse:
properties:
status:
type: string
const: error
title: Status
default: error
message:
type: string
title: Message
description: A description about the given error
type: object
required:
- message
title: ChannableErrorResponse
description: The standard Channable error response
OrderAttachmentUploadResponse:
properties:
status:
$ref: '#/components/schemas/ResponseModelStatus'
order_attachment_id:
anyOf:
- type: integer
- type: 'null'
title: Order Attachment Id
description: Channable ID for the attachment. Is empty on failure
message:
anyOf:
- type: string
- type: 'null'
title: Message
type: object
required:
- status
title: OrderAttachmentUploadResponse
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ResponseModelStatus:
type: string
enum:
- success
- error
- warning
- debug
title: ResponseModelStatus