Skip to content

Designed
Replace specification contacts

Request

Same behaviour as FoodSpecifications_PutContacts, signatory flag included. Full replace of YOUR company's direct contacts on the specification: the retailer's contacts when you are the retailer, the supplier's when you are the supplier. Left untouched: the other party's contacts, contacts that come from a collaboration, and translator contacts. The specification owner stays a contact whether or not it is sent. The response lists exactly that scope, so sending it back unchanged is a no-op (200, nothing written).

Security
oauth2(Required scopes: t1_api)
Path
specificationIdstring, (uuid)required

The unique identifier of the specification

Bodyapplication/jsonrequired
contactsArray of objectsrequired
curl -i -X PUT \
  'https://apis.traceone.com/spec/v2/packaging/specifications/{specificationId}/contacts' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "contacts": [
      {
        "userId": "2c4a230c-5085-4924-a3e1-25fb4fc5965b",
        "isSignatory": true
      }
    ]
  }'

Responses

Your company's direct contacts on the specification, as stored

Bodyapplication/json
contactsArray of objectsrequired
Response
{
  "contacts": [
    { … }
  ]
}