Does SugarCRM have a REST API?
Yes. Current Sugar versions expose a REST API at /rest/v{version}/ that covers standard modules and anything built in Studio, with two-legged OAuth2 for authentication.
Is there an older SOAP API for SugarCRM?
Yes. Sugar's developer guide lists the v1 to v4_1 web services separately as the Legacy API, and older, especially self-hosted, integrations were often written against them in SOAP form. Check which one an existing integration calls before you change anything around it.
Can the Sugar API access custom modules built in Studio?
Yes. Custom modules, fields and relationships from Studio are reachable the same way as standard ones. Custom fields carry a _c suffix in their internal names, which is what the API expects.
Do I need a developer to build on the SugarCRM API?
For anything past a test request, yes. The requests are simple; the work is in a custom platform, token refresh, paging and field mapping, and in handling whatever request limits your instance applies. n-frames writes those integrations.
How long does a SugarCRM access token last?
3,600 seconds, or one hour. The refresh token lasts 1,209,600 seconds, which is 14 days, so a job that runs daily can keep renewing without storing a password.