This page contains information on how to use the Funding Circle Introducer API.

We believe that small businesses deserve access to finance that’s quick and hassle-free.

That’s why we have launched a Funding Circle lending API. Our API makes it fast, simple and straightforward for introducers to offer Funding Circle loans from within their own website, platform or mobile app.

To learn more about our introducer opportunities, visit us at https://www.fundingcircle.com/introducers/. To gain access to our Sandbox, email us at broker@fundingcircle.com.

The API is under OAuth 2.0 Client Credentials Grant flow. In order to make a request, your client must be authorised.

The first step is to generate an access_token. In order to generate this, submit a POST request to the Authentication endpoint passing a base-64 token generated from your unique client_id:client_secret.

curl --request POST \
--url "https://auth.sandbox.api.fundingcircle.co.uk/oauth2/token" \
--header "Authorization: Basic $(echo -n 'client_id:client_secret' | base64)" \
--data-urlencode "grant_type=client_credentials"

The access_token is valid for only 24 hours and must be set in the HTTP header of each request.

Authorization: Bearer eyJraWQiOiJkd1ZKOFFhaGNcL2V4bFBwRUN3TDVNaTA3YmRqOFhNK3MzY.....

Important: You must not include the access_token when making a PUT request to upload a document.

An x-amzn-trace-id header will be returned with each request. We can use this ID to debug problems you may have with a particular API request. Ideally, you should store the x-amzn-trace-id of your requests so you can help us look into a specific one, if required.

We follow the error response format proposed in RFC 7807 also known as Problem Details for HTTP APIs. As with our normal API responses, your client must be prepared to gracefully handle additional members of the response.

• HTTP status: 400

This response means that the API cannot process your request due to something that is perceived to be a client error (e.g., malformed request query, invalid request body, or deceptive request routing). To resolve this, please ensure that the request syntax is correct and includes all mandatory fields.

• HTTP status: 400

This response means that the API cannot process your request due to a wrongly typed or malformed path parameter. To resolve this, please ensure that the parameter value matches the expected pattern.

• HTTP status: 401

This response means that your client is not authorised to access the API. Please make sure you've called the Auth endpoint first to fetch the access_token. Note that each token is valid for only 24 hours.

• HTTP status: 403

This response means that your access_token might be valid, but you're temporarily not allowed to access the API.

• HTTP status: 403

This response means that the API understands the request, but refuses to authorise it. To resolve this, please ensure you have permission to access the resource.

• HTTP status: 404

This response means that the API has processed your request, but the resource could not be found.

• HTTP status: 410

This response means that the API has processed your request, but the resource has now permanently expired.

• HTTP status: 415

This response means that the API refuses to accept the request because of the payload format. To resolve this, please select content-type application/json.

• HTTP status: 422

This response means that the API has processed the request, but the client is not allowed to proceed. Some of the reasons are:

• The email provided is already in use by another Funding Circle non-borrower account.
• We are unable to identify the business provided in our database or the business is dormant or inactive.
• The application cannot be processed because this company either has an ongoing application with Funding Circle, or they have recently been rejected.
• The total percentage of the shares held submitted is less than 50%.

• HTTP status: 424

This response means that the requested action couldn't be performed because it depends on another action that has failed.

Our sandbox environment provides predefined test scenarios using specific values. To test successfully, you must use the exact values listed below - other values will not work as expected.

To test different eligibility outcomes, use one of these specific companies_house_id values in your loan application requests:

• 00000000 - company with low eligibility
• 00000001 - company with medium eligibility
• 00000002 - company with high eligibility

Important: Any other companies_house_id value will return not-eligible, simulating a company that doesn't qualify for Funding Circle products.

To test different loan application journeys, use one of these specific business_name values in your loan application requests:

• Bighead Catshark Ltd - successful application with a credit offer
• Blotchy Swellshark Ltd - application that requires additional documentation
• Loop Shark Ltd - application that remains in processing
• Broadmouth Shark Ltd - rejected application
• Inflight Shark Ltd - error scenario (ongoing application from the same company)

Important: Using any other business name (or no business name) will result in an application that remains in "processing" indefinitely.

Current Limitation: Once you upload and submit documents, the loan application status will change to "in progress" and remain in this status indefinitely.

Submit a complete loan application for a term loan through a simple, step-by-step process. Make a POST request to start the application process and use the returned links to monitor processing status. You will receive either a credit decision or a request for additional information If needed, use our endpoints to securely upload required files.

Some of our endpoints use background processing following the Microsoft Asynchronous Request-Reply Pattern. This means you'll get an immediate response with a placeholder, then you can poll using the provided UUID to get the final result. Most applications receive instant decisions, but some require additional documentation before credit decision can be made. Some endpoints are marked with because they don't have to be called for every application.