Unarchive a supplier
const url = 'https://apibase.ecomweb.app/api/v1/stores/example/suppliers/1/unarchive';const options = {method: 'POST', headers: {'x-api-key': '<x-api-key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://apibase.ecomweb.app/api/v1/stores/example/suppliers/1/unarchive \ --header 'x-api-key: <x-api-key>'Makes an archived supplier live again and returns it with archived_at cleared. Answers 409 with the code SUPPLIER_NAME_TAKEN if a live supplier now uses the same name.
Required scopes: write:purchase_orders
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The supplier ID.
The store’s ref, as returned by GET /stores.
Responses
Section titled “Responses”object
Supplier ID.
Supplier name. Unique among the store’s live suppliers.
Name of the contact person, or null.
Email address that purchase orders are sent to, or null.
Phone number, or null.
First address line, or null.
Second address line, or null.
Province code, or null.
Ward code, or null.
Two-letter country code.
Internal note about the supplier, or null.
When the supplier was archived, as an ISO 8601 timestamp, or null while the supplier is live.
When the supplier was created, as an ISO 8601 timestamp.
When the supplier was last updated, as an ISO 8601 timestamp.
Example generated
{ "id": 1, "name": "example", "contact_name": "example", "email": "example", "phone": "example", "address_line1": "example", "address_line2": "example", "province": "example", "ward": "example", "country": "example", "note": "example", "archived_at": "example", "created_at": "example", "updated_at": "example"}The key is missing, invalid, revoked or expired.
object
The HTTP status code.
What went wrong; validation failures list one message per problem.
The HTTP status text, such as Bad Request.
object
A stable, machine-readable error code.
A human-readable explanation.
Extra context about the error, when there is any.
object
When the error happened, as an ISO 8601 timestamp.
Example generated
{ "statusCode": 1, "message": [ "example" ], "error": "example"}The key may not do this: a missing scope, a readonly key, a publishable key on a Store API route, or a disallowed origin.
object
The HTTP status code.
What went wrong; validation failures list one message per problem.
The HTTP status text, such as Bad Request.
object
A stable, machine-readable error code.
A human-readable explanation.
Extra context about the error, when there is any.
object
When the error happened, as an ISO 8601 timestamp.
Example generated
{ "statusCode": 1, "message": [ "example" ], "error": "example"}The resource does not exist in this store.
object
The HTTP status code.
What went wrong; validation failures list one message per problem.
The HTTP status text, such as Bad Request.
object
A stable, machine-readable error code.
A human-readable explanation.
Extra context about the error, when there is any.
object
When the error happened, as an ISO 8601 timestamp.
Example generated
{ "statusCode": 1, "message": [ "example" ], "error": "example"}The request conflicts with the resource’s current state.
object
The HTTP status code.
What went wrong; validation failures list one message per problem.
The HTTP status text, such as Bad Request.
object
A stable, machine-readable error code.
A human-readable explanation.
Extra context about the error, when there is any.
object
When the error happened, as an ISO 8601 timestamp.
Example generated
{ "statusCode": 1, "message": [ "example" ], "error": "example"}