feat(integrations): Add copper integration #3071
Conversation
dannylwe
changed the title
bodinsamuel
changed the title
docs-v2/integrations/all/copper.mdx
Outdated
|
|
||
| ## API gotchas | ||
|
|
||
| - Copper offers both OAuth and API_KEY authentication modes. To use OAuth2.0 with Copper, you must first register your application. |
There was a problem hiding this comment.
Shouldn't we also add support for the API key auth as well?
There was a problem hiding this comment.
This has been added
docs-v2/integrations/all/copper.mdx
Outdated
| - You will need to provide the name and purpose of your application as well as a URL to an HTTPS endpoint that will handle the secure callback. | ||
| You will receive two credentials, client_id and client_secret, required for all authorization flows. | ||
|
|
||
| - The Dev API uses token based authentication. You have to include the token in the header of every request, along with the email address of the user who generated the token. |
There was a problem hiding this comment.
@dannylwe where in their documentation is this specified? Shouldn't we inject this for the user if this is the case?
There was a problem hiding this comment.
@khaliqgant Makes sense. This should be injected for the user
packages/shared/providers.yaml
Outdated
| auth_mode: OAUTH2 | ||
| proxy: | ||
| base_url: https://api.copper.com/developer_api/ | ||
| docs: https://docs.nango.dev/integrations/all/copper |
There was a problem hiding this comment.
It might be helpful to include the docs link at the end.
|
@khaliqgant, should we also start documenting for |
Yes, absolutely. Thanks for bringing this up. |
|
is it okay to merge? |
No description provided.