Skip to content

Create a vendor

Open .md

POST/v1/api/store/{team_slug}/vendor

v1Operation ID v1_public_vendor_store

Creates a vendor, with its contacts, and returns it with contacts. The first contact you send becomes the primary contact.

A vendor is a supplier you buy from: purchase orders and your products name one.

Permission

Needs the Manage Vendors permission at the level that can create vendors.

Business rules

  • Only the vendor's own fields are checked, as strings. name is not required, and contacts sent here are not checked at all: add a contact with Add a contact to a vendor when you want its fields checked.
  • Vendor names need not be unique.

Path parameters

  • team_slugstringrequired

    Your team slug, shown as Team ID next to your API key in Profile.

    • Example your-team

Request body

application/json, required.

  • Your account number with this vendor.

  • contactarray of objects

    The vendor's contacts. The first one becomes primary.

    Fields of each item (7)
  • A note for the vendor, available on purchase order PDFs.

  • Notes for your team only.

  • namestring

    The vendor's name. Not required by the API (a vendor can be saved without one), but send it: it is how the vendor is shown everywhere.

  • websitestring

    The website address.

Response

200Successful response.

Errors

  • 401The API key is missing or wrong (unauthenticated).

  • 403You are not allowed to do this. api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only {"message": "Insufficient Permission"}. Other refusals use the error envelope, with unauthorized or user_is_not_authorized.

    When
    Your role cannot create vendors. This 403 has a short body, {"message": "Insufficient Permission"}, with no success or error.
    Fix
    Ask a team owner to raise Manage Vendors for your role.
  • 404Not found. page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. code: null, with a message that starts "No query results for": there is no record with that id.

  • 422The request was refused and changed nothing. validation_failed lists what to fix in error.fields; other codes name a business rule, explained in error.message. A few checks answer with only {"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer connect_timeout ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.

    When
    A field has the wrong type. error.code is validation_failed.
    Fix
    Send text fields as strings.