api.mitter.iowith the host that you set, the default being
localhost:11901.Refer the containerization docs for more information.
api.mitter.iois available with only HTTPS. You might currently face issues with our certificate provider - letsencrypt (and its co-signer IdentTrust), as neither of them are trusted roots in the JDK installations prior to Java 8u101 and this problem might exist in other programming environments also. To use SSL with mitter.io APIs, you can either manually add them to the JDK keystore or upgrade to JDK 8u101 and similarly for other environments. We will soon be moving to more widely-trusted SSL providers.
Content-Typeheader is absolutely mandatory in every single request (except multi-part) and no other content-type is supported nor is support for the same planned.
Identifiables in mitter and CRUD operations require and return only the identifier of those entities.
3XXstatus code denotes an error and contains an object with the signature:
POST/PUTrequests with the request a JSON with the shape of the entity that the verb acts on.
GETqueries are speciailised using query parameters and
PATCHrequests have separate entity-diff objects. For instance, a
PUTrequest for application properties is as follows:
PATCHrequest is simply:
Identifiableby Mitter and hence are always associated by a unique ID. Despite being globally unique IDs, they are still namespaced by the application they are a part of, in the sense that there is no supported querying model that allows retrieval or operations upon these entities without requiring the application id.
identifierof the sender is encoded in a single-field object. Instead, if the entity
senderitself was nested within
message, the shape would look like:
identifiernested in all entity objects, such that a standalone identifier object will be a sub-object of the entity object. This will make it easy for clients to use object-merge and object-pick type operations.
messageDatumelements, a key called
linkwhich contains a URI to the image. The URI has a placeholder
$reprwhich is to be replaced by the representation type that was originally requested. For more information refer to the Image Messages section in the reference document.
representationTypefor images is one of the following:
baseThe image that was uploaded as-is.
standardThe image, processed and resized for full-size display with reasonable dimensions.
thumbnailThe image resized to be used as a thumbnail.
301 Moved Permanentlyto point to the CDN. However, there might be a brief interval when the image is not available on the CDN. During this time the endpoint will return a 200 OK with the image data which is stored in an intermediate temporary storage till the upload to S3 takes place.