As part of the Lomavis Publishing API, access can be enabled individually for each profile group. This makes it possible to create posts automatically, either first as a draft or scheduled directly for publishing. Each profile group bundles the associated social media profiles (e.g. Facebook, Instagram, or LinkedIn) and centrally controls which content is published on which channels.
With this API you can efficiently automate workflows for planning posts without having to manually interact with the interface.
Prices can be taken from the price list.
Here you can access details about the API endpoints: Link to the documentation
In the account settings under API access you can retrieve the access key for the API and it has to be set in the Authorization header as follows:
Authorization: Token <API Token>To be able to assign posts to a specific profile group, you first have to fetch the available profile groups. For this, the API for the profile group has to be activated in the connected platforms. After activation, the UUID of the profile group will be shown.
Uploading media consists of three steps that have to be carried out one after the other for each media file. Afterwards, the file can be used in a post.
In the first step, an upload has to be registered using the metadata for the file to be uploaded. The response includes the information for the actual file upload and the subsequent confirmation. You can find more details about the payload and the server response in the documentation.
As part of the request to register an upload, the details for the upload are provided.
{
"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
"headers": {
"Cache-Control": "string",
"x-goog-meta-user-uuid": "5e5f94c8-e5d0-4515-a040-21ae8813bc7f",
"x-goog-meta-main-user-uuid": "c00ff6fc-9bd9-4a51-a329-6dfa13baa367",
"x-goog-meta-upload-uuid": "e83e8c7b-74ed-40fa-b099-f01d859ad81f",
"x-goog-meta-filename": "string",
"x-goog-meta-content-type": "string",
"x-goog-meta-filesize-in-bytes": 0,
"x-goog-meta-media-library-upload": true,
"x-goog-meta-preview-image-upload": true
},
"url": "http://url-to-upload-media-file-to.com",
"confirm_url": "http://url-to-confirm-upload.com"
}With this data, the upload can be carried out. For this, a POST upload as multipart/form has to be performed. It’s important that the request to the URL url is made using the headers from headers. The file has to be sent in the payload with the key file. No additional headers may be set.
File upload via curl:
curl -X POST "http://url-to-upload-media-file-to.com" \
-H "Cache-Control: string" \
-H "x-goog-meta-user-uuid: 5e5f94c8-e5d0-4515-a040-21ae8813bc7f" \
-H "x-goog-meta-main-user-uuid: c00ff6fc-9bd9-4a51-a329-6dfa13baa367" \
-H "x-goog-meta-upload-uuid: e83e8c7b-74ed-40fa-b099-f01d859ad81f" \
-H "x-goog-meta-filename: string" \
-H "x-goog-meta-content-type: string" \
-H "x-goog-meta-filesize-in-bytes: 0" \
-H "x-goog-meta-media-library-upload: true" \
-H "x-goog-meta-preview-image-upload: true" \
-F "file=@/path/to/your_file.jpg"Alternatively, this upload can also be done via a PUT request. This option has to be chosen when working with tools like Make.com or N8N:
curl -X PUT "http://url-to-upload-media-file-to.com" \
-H "Cache-Control: string" \
-H "x-goog-meta-user-uuid: 5e5f94c8-e5d0-4515-a040-21ae8813bc7f" \
-H "x-goog-meta-main-user-uuid: c00ff6fc-9bd9-4a51-a329-6dfa13baa367" \
-H "x-goog-meta-upload-uuid: e83e8c7b-74ed-40fa-b099-f01d859ad81f" \
-H "x-goog-meta-filename: string" \
-H "x-goog-meta-content-type: image/jpeg" \
-H "x-goog-meta-filesize-in-bytes: 0" \
-H "x-goog-meta-media-library-upload: true" \
-H "x-goog-meta-preview-image-upload: true" \
-H "Content-Type: image/jpeg" \
--data-binary "@/pfad/zu/deiner_datei.jpg"After the upload, the upload can be confirmed with a PUT request to the confirm_url.
Confirm file Upload:
curl -X PUT "http://url-to-confirm-upload.com" \
-H "Content-Type: application/json" \
-d '{"success": true}'More details about confirming can be found in the documentation.
After these steps, the file is successfully uploaded and the uuid can be used when creating posts.
With the UUID of the profile group and the UUID of the file upload, posts can be actively scheduled or saved as drafts. Details about the payload can be taken from the documentation here.