Developers API reference Me Sources Mida can read from
Sources Mida can read from GET /me/sources
Base https://api.mockflow.com/v1Scopes user:read
Request
curl https://api.mockflow.com/v1/me/sources \
-H "Authorization: Bearer $MOCKFLOW_API_KEY"
const response = await fetch("https://api.mockflow.com/v1/me/sources" , {
method: "GET" ,
headers: {
Authorization: `Bearer ${process.env.MOCKFLOW_API_KEY}`
}
});
const data = await response.json();
import os, requests
response = requests.get(
"https://api.mockflow.com/v1/me/sources" ,
headers={"Authorization" : f"Bearer {os.environ['MOCKFLOW_API_KEY']}" },
)
response.raise_for_status()
data = response.json()
Response
{
"data" : [
{
"id" : "string" ,
"name" : "Q4 Launch Planning" ,
"category" : "string" ,
"description" : "string" ,
"connected" : false ,
"connectUrl" : "https://app.mockflow.com/board/brd_3f9e2a"
}
],
"note" : "string"
}
{
"error" : {
"code" : "rate_limited" ,
"message" : "Too many requests." ,
"docsUrl" : "https://mockflow.com/developers/concepts/errors#rate_limited"
},
"requestId" : "req_45d49816999bac40"
}
The connectors (Jira, Trello, Slack, Notion and the rest) Mida can pull from in the editor, and which ones this person has connected. Connecting is a browser OAuth flow; the API lists.
Authorization
Authorizationstring header required
Bearer <key>. The key needs user:read scope. Create and manage keys in the developer console ; what each scope unlocks is on the scopes page .
Response 200 · application/json
Was this page helpful? Yes No PreviousMark a notification read Next Spaces