SugarSync · Authentication Profile

Sugarsync Authentication

Authentication

SugarSync uses a custom token‑based authentication flow. A client first obtains a refresh token by POSTing XML credentials (username, password, application ID, accessKeyId, privateAccessKey) to the app‑authorization endpoint. The refresh token is returned in the Location response header. The client then exchanges the refresh token for an access token by POSTing XML (accessKeyId, privateAccessKey, refreshToken) to the authorization endpoint. The access token is also returned in the Location response header and must be sent in the Authorization header of subsequent API calls.

SugarSync declares 2 security scheme(s) across its OpenAPI definitions.

Cloud StorageFile SyncBackupCollaborationBusiness

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

Refresh Token other

Access Token other

Source

Authentication Profile

generated: '2026-10-28'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://www1.sugarsync.com/developer/api/auth-resource/
sources:
- https://www1.sugarsync.com/developer/api/auth-resource/
- https://www1.sugarsync.com/developer/api/method/create-refresh-token/
- https://www1.sugarsync.com/developer/api/method/create-auth-token/
- https://www1.sugarsync.com/developer/get-auth-token-example/
description: SugarSync uses a custom token‑based authentication flow. A client first obtains a refresh token by POSTing XML credentials (username,
  password, application ID, accessKeyId, privateAccessKey) to the app‑authorization endpoint. The refresh token is returned in the Location response
  header. The client then exchanges the refresh token for an access token by POSTing XML (accessKeyId, privateAccessKey, refreshToken) to the
  authorization endpoint. The access token is also returned in the Location response header and must be sent in the Authorization header of subsequent
  API calls.
schemes:
- type: other
  name: Refresh Token
  evidence: To create a refresh token, an application submits an HTTP POST request to the app-authorization endpoint.
  location: body
  how_to_obtain: POST XML containing username, password, application ID, accessKeyId, privateAccessKey to https://api.sugarsync.com/app-authorization;
    token returned in Location header.
- type: other
  name: Access Token
  evidence: To create an access token, an application submits an HTTP POST request to the authorization endpoint.
  location: body
  how_to_obtain: POST XML containing accessKeyId, privateAccessKey, refreshToken to https://api.sugarsync.com/authorization; token returned in
    Location header and used in Authorization header of API calls.
docs: https://www1.sugarsync.com/developer/api/auth-resource/

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/sugarsync-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.