Invite a company to link workspaces
Link a partner workspace works when the other company gives you its Workspace ID. Often you do not have it, and you do not know whether the company uses RekberPay at all. An invitation to link workspaces solves that: RekberPay emails the counterparty's contact, and if that person runs a workspace, they can link it to you with one click. No deal is needed.
The invitation is blind on purpose. You never learn whether the address has a workspace, and a decline looks exactly like no answer.
Before you start
- You are an admin or owner. Invitations are a dashboard action: an API key, workspace or personal, is refused with
403 KEY_NOT_ALLOWED. - Your workspace's Live is unlocked (
409 LIVE_LOCKEDbefore, in either mode). Until then the dashboard shows that invitations open once your business is verified, and you can still link with the partner's Workspace ID. Sandbox never mails anyone outside your workspace: there the call answers as usual but sends and stores nothing. - The counterparty has a contact email (
409 NO_CONTACTwithout one) and is not linked yet (409 ALREADY_LINKED).
1. Send the invitation
In the dashboard, open Counterparties. In the counterparty's row, under RekberPay workspace, choose Email an invite to connect (it shows only when the counterparty has a contact email). The button turns into Send again, with "Invitation sent. We tell you if they accept." and how many of the 5 sends are left.
With a dashboard session, POST /v1/enterprise/counterparties/:id/link-invite with an empty body:
curl -X POST https://api.rekberpay.com/v1/enterprise/counterparties/$COUNTERPARTY_ID/link-invite \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Content-Type: application/json" \
-d '{}'{
"success": true,
"data": {
"message": "Invitation sent to c***@contoh.co.id",
"sends_left": 4,
"next_send_at": "2026-10-22T06:12:00.000Z"
}
}The answer is 202 and the address is masked. The same answer comes back whether or not the address belongs to a RekberPay user. sends_left is how many of the 5 emails remain and next_send_at the earliest next send.
If the email cannot go out, nothing is used: the send is given back, the invitation is not left open, and counterparty.link_invite_refused is written to your activity feed. The call then answers 429 MAIL_LIMIT_REACHED (the contact already got as many emails as RekberPay allows in a day) or 503 INVITES_PAUSED (invitation emails are paused right now). Try again later.
2. Resend, follow up or stop
| Rule | Value |
|---|---|
| Emails per counterparty | 5 in total (429 RESEND_LIMIT_REACHED after that) |
| Time between two emails | At least 1 hour (429 RESEND_TOO_SOON, with Retry-After) |
| Expiry | 14 days after the last email. Each new email moves the expiry |
| Open invitations per counterparty | One. Send again resends it instead of adding another |
GET /v1/enterprise/counterparties/:id/link-invite tells you where it stands:
status | Meaning |
|---|---|
none | Never invited |
sent | Waiting. A company that declined also reads sent until the invitation runs out |
accepted | Linked. The counterparty now shows its workspace |
no_answer | Declined or expired. You cannot tell which |
To withdraw an open invitation, call DELETE /v1/enterprise/counterparties/:id/link-invite. It leaves their Invitations tab and can no longer be accepted. The answer is { "ended": true }, or false when nothing was open. Ending does not give back a send.
If you change the counterparty's contact email, the invitation to the old address can no longer be accepted, and the next send goes to the new address.
3. What the invited company sees
The email goes to the contact address and opens Counterparties, Invitations in the dashboard. If the address already belongs to a RekberPay account, its owner also gets a bell notification. When that person signs in to RekberPay with the same verified email and is an admin or owner of a workspace, the invitation shows on Counterparties, under the Invitations tab (Invitations received), with your workspace name, the name you gave them as a counterparty and the date it stays open until. Nobody else in their workspace sees it, and an invitation from your own workspace never shows.
They choose Accept or Decline. With a dashboard session that is GET /v1/enterprise/link-invites/incoming, then POST /v1/enterprise/link-invites/:id/accept or POST /v1/enterprise/link-invites/:id/decline:
curl https://api.rekberpay.com/v1/enterprise/link-invites/incoming \
-b cookies.txt \
-H "X-Enterprise-Account: $WORKSPACE_ID"{
"success": true,
"data": [
{
"id": "bbbbbbb6-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"workspace_name": "PT Contoh Niaga",
"counterparty_name": "Mitra Kemasan",
"expires_at": "2026-11-05T06:12:00.000Z"
}
]
}curl -X POST https://api.rekberpay.com/v1/enterprise/link-invites/$INVITE_ID/accept \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID"The answer is { "status": "accepted" } (or "declined"). An invitation that expired, was ended or was already answered answers 404 NOT_FOUND, and 409 ALREADY_LINKED means the counterparty was linked to a workspace in the meantime.
A person who does not have a workspace yet can create one first, then accept.
4. After they accept
The link is the same as one made from a Workspace ID:
- Your counterparty record now points at their workspace, in Sandbox and Live.
- Deals you already have with that counterparty become shared deals for them, and your open drafts become fee proposals they answer. See Agree who pays the fee.
- From now on they deliver milestones, answer in the deal room and choose where they are paid from their own dashboard. See Share a deal with your counterparty.
You get the counterparty.linked event in your feed and on your webhooks. The sends themselves are counterparty.link_invited in your activity feed only. Either side can end the link later: End a partner link.
Invitation or deal preview link?
| Invitation to link workspaces | Deal preview link | |
|---|---|---|
| Needs a deal | No | Yes, an activated deal |
| The contact sees | Your workspace name, then Accept or Decline | The deal summary, then joins it |
| Result | A workspace link for all deals | The deal joins their workspace, which links the counterparty |
The full fields and errors are in the Deal room reference.