Skip to main content
Use https://data.grdd.net with Authorization: Bearer <ACCESS_TOKEN>. Get a Core-issued access token for your company. These operations act for the company in that token and require access to the partnership action you request. You cannot choose another company to act for. In a path, {partnershipId} means the other company’s GNET ID, not the request ID. For a confirmed partner, get it from counterpartyCompanyId. For a pending request, get it from counterparty.companyId. Encode the ID as one URL path segment.

Read partnerships

Send no body on these reads. The list and detail routes accept only fresh=true or fresh=false. The default is false. Use fresh=true when you need a refreshed result. The relationship and status routes take no query parameters.
The Connect list returns its fields directly. It does not accept Core’s include, format, fields or force query parameters.
  • confirmed entries have id, subjectCompanyId, counterpartyCompanyId, status: "confirmed" and counterparty. partneredAt can be absent or null.
  • incoming and outgoing entries have id, senderCompanyId, recipientCompanyId, status: "pending" and counterparty. requestId is optional. requestedAt can be absent or null.
  • Each counterparty or access summary includes companyId and name. Other fields can be absent or null.
  • counts has confirmed, incoming and outgoing. fetchedAt is a UTC timestamp.
Keep the Core read reference if you need a separately selected company’s partner list or the old Core request or response format.

Change a partnership

All six writes require an Idempotency-Key of 8 to 128 printable ASCII characters without spaces. They do not require If-Match. Send Content-Type: application/json for send and update. For the other four actions, send no body, not even {}. partnerid is the other company’s GNET ID. Do not send griddid on either JSON write or partnerid in the update body. The optional details accept null or the values below. The body rejects unknown fields. The following example changes a partner record. Replace PARTNER_GNET_ID with the URL-encoded ID of a partner you intend to update. Set WRITE_KEY to a new key for this change.

Write results and recovery

All six writes can return 202. The partnership change succeeded, but follow-up work is pending. Completed 200 and 201 responses, and pending 202 responses, include operationId, counterpartyCompanyId, status and effects. status is completed or pending. Each effect has name, status, retryable and, when available, problemCode. A completed 204 delete has no JSON body. A pending 202 delete does have JSON. There is no partnership operation URL to poll or resume. After a 202, keep the operation ID for support. Read partnership state if you need to check the change. Do not retry with a new key. An exact retry with the same key can replay the recorded response, including a recorded 202. If the first request is still running or used the same key with different data, the API can return 409 idempotency_conflict. On a timeout or an error that leaves the result unknown, check partnership state before starting a new write. See Connect API errors for the problem fields. Use the Core write reference only if your integration still needs its existing wire contract.