Offer your traders PropFirmConnector discounts
The Vendor API lets an approved partner issue single-use discount codes for PropFirmConnector — the NinjaTrader 8 add-on your Rithmic traders use to connect — straight from its own backend, with no customer data shared at issuance and signed webhooks for everything that happens after.
Three calls, one clean boundary
-
Issue a code from your backend
After authenticating your own customer, call
POST /vendor/v1/discount-codeswith an empty body and an idempotency key. You get back a single-useXXXX-XXXXcode and a durablediscount_code_id— and PropFirmConnector learns nothing about who it is for. -
Your customer redeems at checkout
The trader enters the code at PropFirmConnector checkout and gets your offer's discounted plan. New customers keep the normal seven-day free trial; the code is consumed when their license slot activates.
-
Follow the outcome
HMAC-signed webhooks fire on redemption, license status changes, and payment reversals. Status and redemption-list endpoints give you authoritative reconciliation whenever you need it.
The parts your engineers will ask about
No customer PII at issuance
The create request is an empty JSON object — customer identity fields are actively rejected. You map codes to customers privately; PropFirmConnector shares back only a redemption-time profile name and verified email.
Scoped bearer keys, shown once
API keys with per-endpoint scopes, one-way verifier storage, constant-time
comparison, and a two-key rotation overlap for zero-downtime rotation. Production
keys are prefixed pfc_live_.
Safe retries for 12 months
Every create carries an Idempotency-Key. Replays return the same code,
conflicting bodies are rejected, and lost responses are recovered by retrying — never
by re-keying.
Signed, verified, replayable
HMAC-SHA256 over a canonical string with a published byte-exact test vector, challenge-verified endpoints, at-least-once delivery with backoff, and portal-driven replay for exhausted deliveries.
Fail-closed by design
The verified credential — never a request field — selects your vendor and environment. Cross-tenant IDs return 404, cursors are tamper-evident, and webhook events can never be redirected to another tenant.
PII with an expiry date
Redemption identity snapshots are purged 12 months after a license slot goes
inactive, and the canonical object reports pii_purged so your own
cleanup can follow.
An afternoon of backend work
- A server-side call to issue codes when a customer qualifies — authenticated with your bearer key, idempotent by construction.
- A private mapping from your customer to the returned
discount_code_id— the durable bridge you reconcile with later. - A page in your authenticated customer area that shows the code to the customer it was issued for.
- A webhook receiver that verifies the HMAC signature, deduplicates by
event ID, and applies updates in
status_versionorder.
The full v1 reference specifies every header, object, status value, and retry rule — including the signature test vector your receiver can verify byte-for-byte before your first live delivery.
Vendor API questions
Who is the Vendor API for?
Futures prop firms and trading-tool vendors that want to offer their customers a PropFirmConnector discount as a perk. Your backend issues single-use discount codes through a REST API, your customer redeems the code at PropFirmConnector checkout, and you follow the outcome through signed webhooks and status endpoints.
Do I send my customer data to PropFirmConnector?
No. Issuing a code sends no customer ID, name, or email — the create request body is an empty JSON object. You keep the mapping between your customer and the returned discount_code_id on your side. Only after a code is redeemed does PropFirmConnector share back two values: the profile name and verified email of the redeeming PropFirmConnector account.
What does my customer get?
A single-use code for a discounted PropFirmConnector plan defined by your offer, configured during onboarding. New customers keep the normal seven-day free trial before billing starts; customers with prior PropFirmConnector history are charged immediately. Each redeemed code funds one independent license slot.
Can a code be reused or stacked?
No. Codes are single-use, expire on an offer-configured deadline (24 hours for launch offers), apply to one plan, and never combine with another discount. Once a trial activates or a purchase succeeds the code is permanently consumed — refunds, chargebacks, or cancellation never make it reusable.
How do I keep my books in sync?
Webhooks are the primary mechanism: HMAC-SHA256-signed deliveries fire when a code is redeemed, when its license status changes, and when a payment is reversed. Delivery is at-least-once with retries, and the status and redemption-list endpoints remain available for authoritative reconciliation at any time.
How do I test my integration?
Onboarding goes straight to production — there is no separate sandbox to integrate against. The webhook signature scheme ships with a published byte-exact test vector you can verify locally before your first delivery, and your first issued code is walked through end to end with PropFirmConnector so both sides confirm redemption, webhooks, and status reads.
Is there an SDK?
The API is deliberately small: three REST endpoints over HTTPS with JSON, bearer-key authentication, and one webhook signature scheme with a published byte-exact test vector. Any HTTP client works; most integrations are a few dozen lines of backend code.
How do I become a vendor?
Email support@propfirmconnector.com with your firm name and website. Onboarding covers your offer terms, production credentials, and go-live coordination.
Become a PropFirmConnector vendor
Tell us who you are and what you'd like to offer your traders. Onboarding covers your offer terms, production credentials, and go-live coordination.