Automate Flat

What Flat is

The Flat API allows you to easily extend the abilities of the [Flat Platform](https://flat.io), with a wide range of use cases including the following: * Creating and importing new music scores using MusicXML, MIDI, Guitar Pro (GP3, GP4, GP5, GPX, GP), PowerTab, TuxGuitar and MuseScore files * Browsing, updating, copying, exporting the user's scores (for example in MP3, WAV or MIDI) * Managing edu

API host: api.flat.io

What HumDay can do in Flat

47 documented operations change something in Flat.

• POSTCreate a new user account/organizations/users
• POSTPost a new comment/scores/{score}/comments
• POSTCreate a new score/scores
• POSTCreate a new class/classes
• POSTCreate a new collection/collections
• POSTCreate a new invitation to join the organization/organizations/invitations
• PUTAdd a user to the class/classes/{class}/users/{user}
• POSTCreate a new couple of LTI 1.x credentials/organizations/lti/credentials
• POSTAdd a new video or audio track to the score/scores/{score}/tracks
• POSTCreate a new revision/scores/{score}/revisions
• DELETERemove an account from Flat/organizations/users/{user}
• PUTUpdate account information/organizations/users/{user}
• POSTAdd a new collaborator/scores/{score}/collaborators
• DELETERemove a user from the class/classes/{class}/users/{user}
• DELETEDelete a comment/scores/{score}/comments/{comment}
• PUTUpdate an existing comment/scores/{score}/comments/{comment}
• DELETEMark the comment as unresolved/scores/{score}/comments/{comment}/resolved
• PUTMark the comment as resolved/scores/{score}/comments/{comment}/resolved
• DELETEDelete a score/scores/{score}
• PUTEdit a score's metadata/scores/{score}
• PUTUpdate the class/classes/{class}
• POSTAdd a feedback comment to a submission/classes/{class}/assignments/{assignment}/submissions/{submission}/comments
• DELETEDelete the collection/collections/{collection}
• PUTUpdate a collection's metadata/collections/{collection}
• PUTAdd a score to the collection/collections/{collection}/scores/{score}
• POSTFork a score/scores/{score}/fork
• POSTUntrash a score/scores/{score}/untrash
• DELETEUnarchive the class/classes/{class}/archive
• POSTArchive the class/classes/{class}/archive
• POSTActivate the class/classes/{class}/activate
• POSTAssignment creation/classes/{class}/assignments
• POSTJoin a class/classes/enroll/{enrollmentCode}
• POSTUntrash a collection/collections/{collection}/untrash
• DELETERemove an organization invitation/organizations/invitations/{invitation}
• PUTCreate or edit a submission/classes/{class}/assignments/{assignment}/submissions
• DELETERevoke LTI 1.x credentials/organizations/lti/credentials/{credentials}
• DELETERemove an audio or video track linked to the score/scores/{score}/tracks/{track}
• PUTUpdate an audio or video track linked to a score/scores/{score}/tracks/{track}
• DELETEDelete a score from the collection/collections/{collection}/scores/{score}
• DELETEDelete a collaborator/scores/{score}/collaborators/{collaborator}
• POSTCopy an assignment/classes/{class}/assignments/{assignment}/copy
• DELETEUnarchive the assignment./classes/{class}/assignments/{assignment}/archive
• POSTArchive the assignment/classes/{class}/assignments/{assignment}/archive
• DELETEDelete a feedback comment to a submission/classes/{class}/assignments/{assignment}/submissions/{submission}/comments/{comment}
• PUTUpdate a feedback comment to a submission/classes/{class}/assignments/{assignment}/submissions/{submission}/comments/{comment}
• DELETEDelete a submission/classes/{class}/assignments/{assignment}/submissions/{submission}
• PUTEdit a submission/classes/{class}/assignments/{assignment}/submissions/{submission}

What HumDay can read from Flat

These are the operations a schedule or a trigger can watch.

• GETList the classes available for the current user/classes
• GETList liked scores/users/{user}/likes
• GETList user's scores/users/{user}/scores
• GETList the organization users/organizations/users
• GETGet a public user profile/users/{user}
• GETGet current user profile/me
• GETList the collections/collections
• GETList group's users/groups/{group}/users
• GETList comments/scores/{score}/comments
• GETList the organization invitations/organizations/invitations
• GETCount the organization users using the provided filters/organizations/users/count
• GETList LTI 1.x credentials/organizations/lti/credentials
• GETList group's scores/groups/{group}/scores
• GETList the audio or video tracks linked to a score/scores/{score}/tracks
• GETList the revisions/scores/{score}/revisions
• GETList submissions related to the score/scores/{score}/submissions
• GETList the collaborators/scores/{score}/collaborators
• GETList the scores contained in a collection/collections/{collection}/scores
• GETList the submissions for a student/classes/{class}/students/{user}/submissions
• GETGet group information/groups/{group}
• GETGet a score's metadata/scores/{score}
• GETGet the details of a single class/classes/{class}
• GETGet collection details/collections/{collection}
• GETAssignments listing/classes/{class}/assignments
• GETList the students' submissions/classes/{class}/assignments/{assignment}/submissions
• GETList the feedback comments of a submission/classes/{class}/assignments/{assignment}/submissions/{submission}/comments
• GETRetrieve the details of an audio or video track linked to a score/scores/{score}/tracks/{track}
• GETGet a score revision/scores/{score}/revisions/{revision}
• GETGet a collaborator/scores/{score}/collaborators/{collaborator}
• GETGet a score revision data/scores/{score}/revisions/{revision}/{format}
• GETCSV Grades exports/classes/{class}/assignments/{assignment}/submissions/csv
• GETExcel Grades exports/classes/{class}/assignments/{assignment}/submissions/excel
• GETGet a student submission/classes/{class}/assignments/{assignment}/submissions/{submission}
• GETGet the history of the submission/classes/{class}/assignments/{assignment}/submissions/{submission}/history

How automating Flat works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Flat account.
4. Grant access, then go live. You approve the specific Flat operations it may use — and only those.

Popular Flat integrations

Connect Flat to the tools people pair it with most.

• Flat and OData for namespace microsoft.graphintegration
• Flat and Cloudflareintegration
• Flat and NetBoxintegration
• Flat and GitHubintegration
• Flat and Mistintegration
• Flat and Loket.nlintegration
• Flat and Atlassian The Jira Cloud platformintegration
• Flat and Magento B2Bintegration
• Flat and Stripeintegration
• Flat and Zuora Reference Billingintegration
• Flat and bunqintegration
• Flat and DocuSignintegration

Automate Flat with these

• Google Compute Engine694 operations
• Jellyfin379 operations
• OpenAI273 operations
• Evetech EVE Swagger Interface206 operations
• Google Campaign Manager 360205 operations
• Google Content for Shopping175 operations
• Google Display & Video 360151 operations
• Bungie.Net134 operations
• VocaDbWeb127 operations
• Google Admin SDK122 operations
• Google Apigee109 operations
• Shutterstock Explorer109 operations

Categories

• Media
• Collaboration

Questions about Flat automation

Can HumDay connect to Flat?

Yes. HumDay reads Flat's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 81 operations are documented.

Do I need to write code to automate Flat?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Flat account.

What can HumDay do in Flat?

47 of the 81 documented operations change something in Flat, and 34 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Flat account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Flat is held behind that approval.

Where this came from

The operations above are read from a published API description for Flat at raw.githubusercontent.com/FlatIO/api-reference/master/spec/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-07-26.