Getting Started
/
Glossary
Glossary
This page provides definitions of terms frequently used in the MORI Developer Center.
Understanding each term precisely will make it much easier to integrate and use the API.
Application
It refers to the client’s service that wants to apply the AI training prevention feature — in other words, the app to be integrated.
In this documentation, it is referred to simply as the “app” or “application.”
Access Token
It is a token issued after authentication is completed using the OAuth 2.0 method.
You must use this token to call the API — it acts as a security mechanism ensuring that only authenticated users can access the MORI API.
When making an API request, this token must be included in the request header.
API
An API is a set of communication rules that allow the MORI service and the client’s app to exchange data.
Through these rules, the two systems can interact and communicate with each other.
API Domain
To test or use MORI’s API in a production environment, you need to know the server address (API_DOMAIN).
For example, the production endpoint is as follows:
{{PRODUCTTION API_DOMAIN}}
https://morimori.app
Webhooks
A webhook is a mechanism that automatically notifies the client’s app when an event occurs on the server.
While APIs typically work in a “polling” manner, where the client repeatedly requests updates from the server, webhooks operate like “push notifications,” where the server proactively sends updates to the client.
For example, if someone uploads a file, that information can be sent immediately through a webhook.
This enables real-time processing and reduces unnecessary API calls.
Idempotency
Idempotency refers to the property of an operation that produces the same result even if the same request is sent multiple times.
For example, if a request fails due to a network issue and needs to be retried, idempotency ensures that resending the same request will be processed exactly once without duplication.
APIs with this property are more reliable and help prevent unexpected errors or duplicate processing.
Some of MORI’s APIs also support idempotency.
Getting Started
/
Glossary
Glossary
This page provides definitions of terms frequently used in the MORI Developer Center.
Understanding each term precisely will make it much easier to integrate and use the API.
Application
It refers to the client’s service that wants to apply the AI training prevention feature — in other words, the app to be integrated.
In this documentation, it is referred to simply as the “app” or “application.”
Access Token
It is a token issued after authentication is completed using the OAuth 2.0 method.
You must use this token to call the API — it acts as a security mechanism ensuring that only authenticated users can access the MORI API.
When making an API request, this token must be included in the request header.
API
An API is a set of communication rules that allow the MORI service and the client’s app to exchange data.
Through these rules, the two systems can interact and communicate with each other.
API Domain
To test or use MORI’s API in a production environment, you need to know the server address (API_DOMAIN).
For example, the production endpoint is as follows:
{{PRODUCTTION API_DOMAIN}}
https://morimori.app
Webhooks
A webhook is a mechanism that automatically notifies the client’s app when an event occurs on the server.
While APIs typically work in a “polling” manner, where the client repeatedly requests updates from the server, webhooks operate like “push notifications,” where the server proactively sends updates to the client.
For example, if someone uploads a file, that information can be sent immediately through a webhook.
This enables real-time processing and reduces unnecessary API calls.
Idempotency
Idempotency refers to the property of an operation that produces the same result even if the same request is sent multiple times.
For example, if a request fails due to a network issue and needs to be retried, idempotency ensures that resending the same request will be processed exactly once without duplication.
APIs with this property are more reliable and help prevent unexpected errors or duplicate processing.
Some of MORI’s APIs also support idempotency.
Getting Started
/
Glossary
Glossary
This page provides definitions of terms frequently used in the MORI Developer Center.
Understanding each term precisely will make it much easier to integrate and use the API.
Application
It refers to the client’s service that wants to apply the AI training prevention feature — in other words, the app to be integrated.
In this documentation, it is referred to simply as the “app” or “application.”
Access Token
It is a token issued after authentication is completed using the OAuth 2.0 method.
You must use this token to call the API — it acts as a security mechanism ensuring that only authenticated users can access the MORI API.
When making an API request, this token must be included in the request header.
API
An API is a set of communication rules that allow the MORI service and the client’s app to exchange data.
Through these rules, the two systems can interact and communicate with each other.
API Domain
To test or use MORI’s API in a production environment, you need to know the server address (API_DOMAIN).
For example, the production endpoint is as follows:
{{PRODUCTION API_DOMAIN}}
https://morimori.app
Webhook
A webhook is a mechanism that automatically notifies the client’s app when an event occurs on the server.
While APIs typically work in a “polling” manner, where the client repeatedly requests updates from the server, webhooks operate like “push notifications,” where the server proactively sends updates to the client.
For example, if someone uploads a file, that information can be sent immediately through a webhook.
This enables real-time processing and reduces unnecessary API calls.
Idempotency
Idempotency refers to the property of an operation that produces the same result even if the same request is sent multiple times.
For example, if a request fails due to a network issue and needs to be retried, idempotency ensures that resending the same request will be processed exactly once without duplication.
APIs with this property are more reliable and help prevent unexpected errors or duplicate processing.
Some of MORI’s APIs also support idempotency.
Getting Started
Integration Guide