update api links #4097
Merged
update api links #4097
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rchinn1
added
the
content-update
rchinn1
reviewed
Jan 21, 2023
src/partners/enable-with-segment.md
Outdated
| @@ -2,25 +2,25 @@ | |||
| title: Enable with OAuth | |||
| --- | |||
|
|
|||
| Enable with OAuth, supported with the [Public API](/docs/api/public-api), allows partners to build seamless flows for customers to implement and enable integrations within their workspace. This is a [post-launch requirement](/docs/partners/#post-launch) for a partner to graduate from public beta to public. | |||
| Enable with OAuth, supported with the [Config API](/docs/api/config-api), allows partners to build seamless flows for customers to implement and enable integrations within their workspace. This is a [post-launch requirement](/docs/partners/#post-launch) for a partner to graduate from public beta to public. | |||
There was a problem hiding this comment.
Hey @tcgilbert, just want to confirm that graduating from public beta to public is correct, as opposed to something like private beta to public.
There was a problem hiding this comment.
"public beta to public" is the standard we set for dev center 1.0 destinations. It is slightly different with 2.0 integrations, in that there is no enable with oauth requirement.
Being that 1.0 is legacy I'd be okay with removing the last sentence entirely:
- "This is a post-launch requirement for a partner to graduate from public beta to public."
There was a problem hiding this comment.
Thanks for clarifying. I removed the last sentence and will include these updates in our next deploy.
rchinn1
approved these changes
Jan 23, 2023
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Looks like there was a site wide change to update any mention of the "Config API" with the "Public API" back in september. Unfortunately, the tokens generated from the "enable with oauth" flow are only compatible with the config api, so this has caused some confusion for partners with 1.0 integrations.
Merge timing
asap