Partner onboarding
Fandation partner access isn’t self-service. Contact Fandation Support to register your integration before implementing or testing an OAuth or Public Documents API integration.
Onboarding process
Section titled “Onboarding process”flowchart TD
contact[Contact Fandation Support to register the integration]
provide[Provide application and contact information]
review[Fandation reviews the integration]
provision[Fandation provisions the required credentials and configuration]
credentials[Receive credentials and environment-specific endpoints]
configure[Configure and test the integration]
oauth[Begin per-user OAuth authorization]
publicDocuments[Call the Public Documents API]
contact --> provide --> review --> provision --> credentials --> configure
configure --> oauth
configure --> publicDocuments
Information to provide
Section titled “Information to provide”Provide Fandation with:
- Your company or partner name
- Your application name
- Your application website
- A technical contact email
- A support contact or support URL
- Your privacy-policy URL
- Your requested environment, such as development or production
- The integration path you need, OAuth authorization or the Public Documents API
OAuth integrations also need one or more exact redirect URIs.
Fandation may also request:
- Your application logo
- Your terms-of-service URL
- A security contact
- Your expected request volume
What Fandation provides
Section titled “What Fandation provides”After review and approval, Fandation provides the credentials and endpoint information that match the approved integration path.
OAuth integrations receive:
- A client ID
- A client secret
- The registered redirect URI configuration
Public Documents API integrations receive:
- An environment-specific API key
- Environment-specific endpoint information
Every credential is a confidential backend secret. Don’t place a client secret or API key in browser code, a client-side application, or source control.
Next step
Section titled “Next step”After Fandation confirms that the integration is ready, continue to configure the OAuth integration or read the Public Documents API guide.