Partnero

Affiliate, referral and partner program management — partnero.com.

Docs index: https://docs.partnero.com/llms.txt API reference: https://docs.partnero.com/api-reference/introduction.md

Auth

A Bearer API key from Integration → API, generated inside a program. The key is scoped to that one program, which is why no step in this piece asks which program to use.

Actions

| Action | Endpoint | |---|---| | Create Partner | POST /v1/partners | | Get Partner | GET /v1/partners/{id} | | List Partners | GET /v1/partners | | Create Customer | POST /v1/customers | | Create Transaction | POST /v1/transactions | | Create Partner Sign-In URL | POST /v1/partners:sign-in-url |

Triggers

All four are real webhooks — Partnero exposes a subscription API, so each trigger registers itself on enable (POST /v1/webhooks) and removes itself on disable (DELETE /v1/webhooks/{key}). There is no manual dashboard step.

| Trigger | Event | |---|---| | New Partner | partner.created | | Partner Approved | partner.approved | | New Customer | customer.created | | New Transaction | transaction.created |

Notes

• Partner identification is a three-way choice. Create Customer and Create Partner Sign-In URL accept a partner ID, referral key or email; Partnero resolves them in that order and needs at least one. Both actions check locally rather than relaying a 422.
• Transaction Key is worth setting. It is what allows a later refund to reverse the right commission.
• Rewardable / Already Rewarded are three-state dropdowns, not checkboxes. Both default on Partnero's side, and an untouched checkbox saves as false — which would silently make every transaction unrewardable.
• Partner portal passwords are not exposed. POST /partners accepts a password, but Partnero auto-generates one and a password typed into a flow input would be stored in the flow.
• Webhook signing secrets are not stored. POST /webhooks returns a signature used for HMAC verification; nothing here verifies signatures, so it is dropped rather than kept.