Skip to main content

Content Moderation

SDK

We provide a PHP SDK with an example of integration to make it easier and fast to get ready to moderate your content:

VerifyMyContent Content Moderation PHP SDK

Postman Workspace

We've created a Postman workspace specifically for our API, which contains example API calls that you can use to test and familiarise yourself with our API.

The workspace includes example API calls for each of our API endpoints, along with detailed descriptions of the request parameters and headers being used.

You can generate most of the client code to call our APIs using the Postman client code generator. With this feature, developers can select a range of programming languages, and generate the corresponding code with a few clicks.

Please note that while both the example API calls and the generated code can be a helpful starting point, it's important to thoroughly test your own API calls before deploying them in production. If you encounter any issues while using the example API calls, or if you have any questions about our API, please don't hesitate to reach out to our support team.

API Domain

Our API is designed to be used in two environments: a sandbox environment and a production environment.

The sandbox environment is intended for testing and development purposes, while the production environment is used for live data and real-world use cases.

To ensure the security and integrity of our API, we use separate API keys for each environment. This means that you will need to obtain different API keys for the sandbox and production environments, and should not use the same key for both.

DomainEnvironment
https://moderation.verifymycontent.comproduction
https://moderation.sandbox.verifymycontent.comsandbox

Generating the HMAC header

To improve the security of the communication between your implementation and the VerifyMyContent API, we require you to generate a unique hexadecimal encoded SHA256 HMAC hash for each request, based on the input parameters.

The process of generating it depends on the language of your implementation.

If you use our SDK, the HMAC step will be abstracted,
and you don't need to do anything related to it.
Copy

Copied!

<?php

hash_hmac('sha256', $input, 'API_SECRET');
Copy

Copied!

import { HmacSHA256 } from 'crypto-js';

HmacSHA256(JSON.stringify(input), 'API_SECRET').toString()
Copy

Copied!

Integration Steps

The VerifyMyContent content moderation consists of 2 basic steps:

  1. Verifying the uploader

  2. Moderating the content itself

When you call the Start Moderation endpoint, it will take care of both steps, and you will receive the moderation status updates on the URL you've set as a webhook.

Alternatively, the Current status of the moderation endpoint is available for you to get the status, if you prefer not to use a webhook.

The meaning of each status

When you start the moderation, the content will have the status Awaiting People, which means that we need to verify the identity of the uploader and confirm they have received the consent of any participants appearing in the content.

If face analysis is enabled after uploader verification the content will change to Face Analysis, the content is now passing through our AI to check if there is someone in the content other than the uploader. If there is someone that have not give the uploader consent the content will change to Awaiting Participant, which means that the uploader should now add other participants. After the participants added the status change to either Awaiting Consent, waiting for participants added give their consent, or to Awaiting Automation.

As soon as the uploader is verified and they confirm they have received the consent of any participants, the content status will change to Awaiting Automation, which will trigger our AI to moderate the content and check that it does not contain any content that should not be published. If we cannot download the video or image you sent, the content will finish the process with the status Failed.

After the AI, the status will change to Awaiting Moderation, and the human moderation is triggered.

Once the content has passed human moderation the status will change to either Approved if the content can be published or Rejected if it cannot be published.

Content Moderation Flow

Start Moderation

To start the moderation, you'll need to send us the original video or image uploaded by your customer, some data from your customer so we can trigger reminders and notifications during the process, and a webhook to notify you when the moderation status changes.

Important: Please generate a universally unique identifier (UUID v4) for each customer on your site. You should then use this same customer ID every time you call one of our APIs on behalf of that customer. This UUID should never change. For example, if the customer's username on your site changes, their UUID shouldn't.

Authorization Header

Generate HMAC with: Request Body
Authorization: hmac YOUR-API-KEY:GENERATED-HMAC

Request parameters

content required

Information about the content being moderated.

type optional

It can be video or image. Defaults to video.

external_id required

A unique identifier on your side to correlate with this moderation.

url required

The URL where we can download the original video or image uploaded by your customer.

title optional

The title of the content being moderated.

description optional

The text written by your customer to describe the content.

redirect_url optional

The URL where we are going to redirect your customer after the moderation is done.

webhook required

This is the URL where we are going to post status updates of the moderation

customer required

Customer information

id required

Customer's unique ID

email required

Customer's email address

phone optional

Customer's phone number

type optional

It can be one of these values. It defaults to moderation.

TypeDescription
moderationWe will look for any illegal harmful content. This is also the default option when you don’t send any value.
face-matchWe will look to see if the expected people are present in the content.
combinedWe will look for any illegal harmful content and to see if the expected people are present in the content via face-match.

Response parameters

id

Unique identifier generated by the VerifyMyContent API

redirect_url

URL you’ll need to redirect the user to start the moderation process.

NOTE: If face analysis is enabled and status is Awaiting Participants, this will be the redirect URL for the uploader to add participants.

external_id

The unique identifier you have sent to correlate this moderation

status

It represents the current status of the moderation flow. It can be one of the following:

StatusDescription
Awaiting PeopleWaiting to verify the identity of the uploader.
Face AnalysisOur AI is about to process the content to detect any unknown person and request the uploader for participant information.
Awaiting ParticipantWaiting for the uploader to confirm the participants and provide the necessary information.
Awaiting ConsentWaiting to verify the identity of the participants and confirm they have given consent to the content being published.
Awaiting AutomationOur AI is about to process the content to detect any illegal or non-consensual content
Awaiting ModerationThe moderators are about to confirm the moderation decision.
ApprovedAll participants consented to the publishing of the content. Please check the warning section to see if any unexpected people were detected in the content.
FailedAn error occurred during the content processing.
RejectedThe content cannot be published as one or more of the participants in the content were unable or unwilling to verify their identity or consent.

notes

Any notes associated with the moderation when the moderation status is 'Failed'

tags

Any tags associated with the moderation when the moderation status is Rejected.

created_at

The date and time in the UTC timezone when the moderation was created

updated_at

The date and time in the UTC timezone when the moderation was updated

Error responses

CodeDescription
400
{"message": "field <field_name> not found", "status_code": 400}
Copy

Copied!

422
{"message": "invalid parameter", "status_code": 422}
Copy

Copied!

401
{"message": "invalid authorization", "status_code": 401}
Copy

Copied!

401
{"message": "Missing Api Key", "status_code": 401}
Copy

Copied!

409
{"message": "request to moderate content ID <content_id> with URL <url> for customer ID <customer_id> already made", "status_code": 409}
Copy

Copied!

500
{"message": "Internal Server Error","status_code": 500}
Copy

Copied!

API Call
POST /api/v1/moderation HTTP/1.1
Content-Type: application/json
Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-BODY

{
    "content": {
        "type": "video",
        "external_id": "YOUR-VIDEO-ID",
        "url": "https://example.com/video.mp4",
        "title": "Your title",
        "description": "Your description"
    },
    "webhook": "https://example.com/webhook",
    "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC",
    "customer": {
        "id": "YOUR-USER-ID",
        "email": "person@example.com",
        "phone": "+4412345678"
    },
    "type": "moderation",
}
Copy

Copied!

curl -d '{"content": {"type": "video", "external_id": "YOUR-VIDEO-ID", "url": "https://example.com/video.mp4", "title": "Your title", "description": "Your description"}, "webhook": "https://example.com/webhook", "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC", customer": {"id": "YOUR-USER-ID", "email": "person@example.com", "phone": "+4412345678"}, "type": "moderation"}' \
-H "Content-Type: application/json" \
-H "Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-BODY" \
-X POST https://moderation.sandbox.verifymycontent.com/api/v1/moderation
Copy

Copied!

<?php
require(__DIR__ . "/vendor/autoload.php");

use \VerifyMyContent\VideoModeration\Moderation;
use \VerifyMyContent\SDK\ContentModeration\Entity\Requests\CreateStaticContentModerationRequest;

$moderation = new Moderation(getenv('VMC_API_KEY'), getenv('VMC_API_SECRET'));
//$moderation->useSandbox();

$response = $moderation->start(new CreateStaticContentModerationRequest([
    "content" => [
      "type" => "video",
      "external_id" => "YOUR-VIDEO-ID",
      "url" => "https://example.com/video.mp4",
      "title" => "Uploaded video title",
      "description" => "Uploaded video description",
    ],
    "request_url" => "https://app.verifymycontent.com/v/ABC-123-5678-ABC",
    "webhook" => "https://example.com/webhook",
    "customer" => [
      "id" => "YOUR-CUSTOMER-UNIQUE-ID",
      "email" => "person@example.com",
      "phone" => "+4412345678"
    ]
]));
Copy

Copied!

Response 201: (application/json)
{
  "id": "ABC-123-5678-ABC",
  "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC",
  "external_id": "YOUR-CORRELATION-ID",
  "status": "Awaiting Automation",
  "notes": "Harmful content found.",
  "tags": null,
  "created_at": "2020-11-12 19:06:00",
  "updated_at": "2020-11-12 19:06:00",
  "consent_type": "simple"
}
Copy

Copied!

Get current status of the moderation

When you already have the id of a moderation you can see the current details of the moderation.

Authorization Header

Generate HMAC with: Request URI
Authorization: hmac YOUR-API-KEY:GENERATED-HMAC

Response parameters

id

Unique identifier generated by the VerifyMyContent API

redirect_url

URL you’ll need to redirect the user to start the moderation process.

NOTE: If face analysis is enabled and status is Awaiting Participants, this will be the redirect URL for the uploader to add participants.

external_id

The unique identifier you have sent to correlate this moderation

status

It represents the current status of the moderation flow. It can be one of the following:

StatusDescription
Awaiting PeopleWaiting to verify the identity of the uploader.
Face AnalysisOur AI is about to process the content to detect any unknown person and request the uploader for participant information.
Awaiting ParticipantWaiting for the uploader to confirm the participants and provide the necessary information.
Awaiting ConsentWaiting to verify the identity of the participants and confirm they have given consent to the content being published.
Awaiting AutomationOur AI is about to process the content to detect any illegal or non-consensual content
Awaiting ModerationThe moderators are about to confirm the moderation decision.
ApprovedAll participants consented to the publishing of the content. Please check the warning section to see if any unexpected people were detected in the content.
FailedAn error occurred during the content processing.
RejectedThe content cannot be published as one or more of the participants in the content were unable or unwilling to verify their identity or consent.

notes

Any notes associated with the moderation when the moderation status is 'Failed'

tags

Any tags associated with the moderation when the moderation status is Rejected.

created_at

The date and time in the UTC timezone when the moderation was created

updated_at

The date and time in the UTC timezone when the moderation was updated

Error responses

CodeDescription
401
{"message": "invalid authentication", "status_code": 401}
Copy

Copied!

403
{"message": "Permission denied", "status_code": 403}
Copy

Copied!

404
{"message": "no results found", "status_code": 404}
Copy

Copied!

500
{"message": "Internal Server Error","status_code": 500}
Copy

Copied!

API Call
GET /api/v1/moderation/{ID} HTTP/1.1
Content-Type: application/json
Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-URI
Copy

Copied!

curl -H "Content-Type: application/json" \
-H "Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-URI" \
https://moderation.sandbox.verifymycontent.com/api/v1/moderation/{ID}
Copy

Copied!

<?php
require(__DIR__ . "/vendor/autoload.php");

use \VerifyMyContent\VideoModeration\Moderation;

$moderation = new Moderation(getenv('VMC_API_KEY'), getenv('VMC_API_SECRET'));
//$moderation->useSandbox();

$response = $moderation->get('ID');
Copy

Copied!

Response 200: (application/json)
{
  "id": "ABC-123-5678-ABC",
  "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC",
  "external_id": "YOUR-CORRELATION-ID",
  "status": "Awaiting Automation",
  "notes": "Harmful content found.",
  "tags": null,
  "created_at": "2020-11-12 19:06:00",
  "updated_at": "2020-11-12 19:06:00",
  "consent_type": "simple"
}
Copy

Copied!

Receive the current status of the moderation

The same information that you can get on the moderation detail API can also be sent via webhook to your domain if you send it to us when you create a moderation.

Authorization Header

Generate HMAC with: Request Body
Authorization: hmac YOUR-API-KEY:GENERATED-HMAC

Request parameters

id

Unique identifier generated by the VerifyMyContent API

redirect_url

URL you’ll need to redirect the user to start the moderation process.

NOTE: If face analysis is enabled and status is Awaiting Participants, this will be the redirect URL for the uploader to add participants.

external_id

The unique identifier you have sent to correlate this moderation

status

It represents the current status of the moderation flow. It can be one of the following:

StatusDescription
Awaiting PeopleWaiting to verify the identity of the uploader.
Face AnalysisOur AI is about to process the content to detect any unknown person and request the uploader for participant information.
Awaiting ParticipantWaiting for the uploader to confirm the participants and provide the necessary information.
Awaiting ConsentWaiting to verify the identity of the participants and confirm they have given consent to the content being published.
Awaiting Face matchOur AI is about to process the content to detect any person who should not be in the content.
Awaiting ModerationThe moderators are about to confirm the moderation decision.
ApprovedAll participants consented to the publishing of the content. Please check the warning section to see if any unexpected people were detected in the content.
FailedAn error occurred during the content processing.
RejectedThe content cannot be published as one or more of the participants in the content were unable or unwilling to verify their identity or consent.

notes

Any notes associated with the moderation when the moderation status is 'Failed'

tags

Any tags associated with the moderation when the moderation status is Rejected.

created_at

The date and time in the UTC timezone when the moderation was created

updated_at

The date and time in the UTC timezone when the moderation was updated

Webhook Call
POST /your-path HTTP/1.1
Host: https://your-domain.com
Content-Type: application/json
Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-BODY

{
    "id": "ABC-123-5678-ABC",
    "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC",
    "external_id": "YOUR-CORRELATION-ID",
    "status": "Rejected",
    "notes": "Harmful content found.",
    "tags": [
      "UNDERAGE"
    ],
    "created_at": "2020-11-12 19:06:00",
    "updated_at": "2020-11-12 19:06:00",
    "consent_type": "simple"  
}
Copy

Copied!

curl -d '{"id": "ABC-123-5678-ABC", "redirect_url": "https://app.verifymycontent.com/v/ABC-123-5678-ABC", "external_id": "YOUR-CORRELATION-ID", "status": "Rejected", "notes": "Harmful content found.", "tags": ["UNDERAGE"], "created_at": "2020-11-12 19:06:00", "updated_at": "2020-11-12 19:06:00"}' \
-H "Content-Type: application/json" \
-H "Authorization: hmac YOUR-API-KEY:GENERATE-HMAC-WITH-REQUEST-BODY" \
-X POST https://your-domain.com/your-path
Copy

Copied!

Response 2xx