Authenticate to ServiceM8 and create a job together with its job activities via the API

Steps

1. Complete the OAuth2 flow (authorization code) to obtain access and refresh tokens, or use a static API key for simpler server-to-server access, depending on which auth model your integration needs
2. Include the access token as a bearer token on the Authorization header (or as a POST parameter, per ServiceM8's supported auth patterns) on every API call
3. POST to the Job endpoint to create the job record; a UUID is optional — if omitted, ServiceM8 generates one and returns it in the x-record-uuid response header
4. POST to the JobActivity endpoint (requires the manage_schedule OAuth scope) to attach schedule/activity entries to the job, again letting ServiceM8 generate the UUID if you don't supply one
5. Read back the job and its activities to confirm the relationship (job UUID referenced correctly on the activity record)
6. Request only the OAuth scopes you actually need (e.g. create_jobs, manage_schedule) since ServiceM8 scopes access narrowly per resource type