Skip to content

Commit 9f7d1c9

Browse files
author
Thomas Gilbert
committed
update api links
1 parent 4b02f23 commit 9f7d1c9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/partners/enable-with-segment.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
title: Enable with OAuth
33
---
44

5-
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.
5+
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.
66

77
## Concepts
88

99
Before getting started with your implementation, it's important to understand the below concepts.
1010

1111
### Apps
1212

13-
As a partner developing an integration using Segment's Public API, everything starts from an **App**. An App behaves like a standard OAuth client, but adds granular permissions. When a user installs your App through the familiar OAuth flow, Segment requires the user to grant access to a specific workspace and source. The user must also be a Workspace Owner of the authorized workspace.
13+
As a partner developing an integration using Segment's Config API, everything starts from an **App**. An App behaves like a standard OAuth client, but adds granular permissions. When a user installs your App through the familiar OAuth flow, Segment requires the user to grant access to a specific workspace and source. The user must also be a Workspace Owner of the authorized workspace.
1414

1515
As a destination partner, you may only manage your own destination on the workspace and source authorized by the user.
1616

@@ -188,7 +188,7 @@ If you created an App with a more permissive scope, you have access to more APIs
188188
- With the `workspace` scope you can change all resources
189189
- With the `workspace:read` you can read all resources, but not change them
190190

191-
A full list of APIs are here: https://segment.com/docs/api/public-api/
191+
A full list of APIs are here: https://segment.com/docs/api/config-api/
192192

193193
The example below shows how you would get a users workspace if you had any of the above scopes:
194194

@@ -306,4 +306,4 @@ When the app was installed, you should have received a Segment `workspace` and
306306

307307
### OK I managed to create an App. How do I use your APIs?
308308

309-
See [the API docs](/docs/api/public-api/).
309+
See [the API docs](/docs/api/config-api/).

0 commit comments

Comments
 (0)