You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
Documenting the partner API provisioning flow in a more consolidated form. So essentially if we were to add a new 'EdReady-like' partner - what would all be required from dev and API calls to get that partner up and running.
what API calls are required to set up a partner and provision them a key
what additional parts of the codebase would need to be updated in order to add customization for a new partner (or can it exclusively be handled via the API calls)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Documenting the partner API provisioning flow in a more consolidated form. So essentially if we were to add a new 'EdReady-like' partner - what would all be required from dev and API calls to get that partner up and running.
what API calls are required to set up a partner and provision them a key
what additional parts of the codebase would need to be updated in order to add customization for a new partner (or can it exclusively be handled via the API calls)
The text was updated successfully, but these errors were encountered: