Knowledge Base

Answers to common questions about the Prokure API.

Getting started

What is the Prokure API?Programmatic access to the opportunities Prokure has matched for your company, and the reasoning behind each match.

Getting your API keyMint a pk_live_ key in the portal, choose its scopes, and copy the secret before it disappears.

Making your first requestSend your key in an Authorization header and read your first page of matched opportunities.

Working with opportunities

Understanding match scoresWhat an opportunity's score means, what score_source tells you about how it was reached, and why estimated_value is usually empty.

Filtering and paginationNarrow the opportunity list with status, score and deadline filters, then walk the results with the opaque cursor.

Archiving and restoring opportunitiesMove an opportunity out of your working list and bring it back, and where archived items go.

Sending match feedbackTell Prokure whether a match verdict was right, and read what the response says about re-scoring.

Asking Prok about an opportunityAsk a question about one solicitation and get a plain-text answer grounded in what Prokure already holds on that notice.

Access & security

Sessions vs API keysTwo credentials reach the Prokure API. Which one each route expects, and why a key cannot manage keys.

Scopes explainedThe six Prokure scopes, how they are chosen, and how to find out which one a route is asking for.

Rotating and revoking keysSwap a Prokure API key without downtime, and what happens the moment you revoke one.

Troubleshooting

Fixing 401 and 403 errorsTell a rejected credential apart from a missing scope, and fix the right one.

Handling 429 rate limitsWhy the limits are counted per IP rather than per key, which headers report your budget, and how to back off.

Why an opportunity isn't in your listThe filters, views and polling habits that hide an opportunity you expected to see.