Table of Contents

Target image management

Targets can be managed in the following two ways:

  • Visual management: Log in to the EasyAR developer center for manual maintenance.
  • API automated management: Integrate into your own business system or management backend by calling the Web Service REST API.
Important

In the cloud recognition service, target image management and image recognition are two different requirements, and the API corresponds to two different Cloud URL endpoints.

Data center region selection

The data center where the gallery example runs supports the following region selections:

  • China-Shanghai
  • US-Silicon Valley

Method 1: Manage target images in the EasyAR developer center

Suitable for small-scale testing or quick manual uploads. Follow these steps:

  1. Log in to the EasyAR developer center and navigate to Cloud recognition management.
  2. Select the target region. If you haven't created an image library yet, create a new one and enable cloud recognition.
  3. Click Manage in the image library list to enter the target image maintenance interface for uploading, modifying, or deleting.

create-web

Method 2: Use rest api for automated management

For applications that need to process a large number of target graphs, it is recommended to use the Web Service REST API to implement automated processes in your application or management backend.

Preparation checklist

The following is the preparation checklist. Before you start managing the target images, you need to prepare a new cloud recognition database instance (Cloud Database)

  • CRS AppId
  • API Key / API Secret or Token
  • Cloud URL
    • Server-end URL: the target image management URL address, https uses port 443
    • Client-end URL: the image recognition service URL address, https uses port 8443
Important

Port distinction note: the target management API entry (443) and the mobile/Unity-called cloud recognition API entry (8443) are two different channels. Please distinguish them when configuring.

How to obtain each item in the checklist

  • CRS AppId viewing method:
    Developer Center -> Cloud Recognition Management -> Select Image Library -> Manage -> Key

m1-appid

  • API Key / API Secret viewing method:
    Developer Center -> Cloud Service APIKey -> Copy

m1-apikey

    If you do not have an API Key yet, create an APIKey and ensure that the Cloud Recognition (CRS) permission is selected. For more information about API Key and permission control, refer to the topic API Key Introduction

m1-apikey-cr

  • Token viewing method:
    Developer Center -> Cloud Service APIKey -> Manage -> Select Validity Period -> Generate Token -> Copy

m1-token

    If you need to customize the validity period of the Token, you can refer to the UAC API —— Create Token method, using the original APIKey and APISecret to create a Token

  • Cloud URL viewing method:
    The target image management in the image library uses the Server-end URL on port 443, Server-end URL
    Developer Center -> Cloud Recognition Management -> Select Image Library -> Manage -> Key -> Image Library Management

m1-server-url

Multi-end integration guide

In actual workflows, target image management is usually integrated into the developer's business server, mobile app, or Unity:

  • Business service platform: Provides sample code for calling APIs in common server development languages (Curl/Java/NodeJS/PHP) to help developers achieve automatic upload and metadata (Meta) updates of target images.

  • Mobile app (Unity/Mobile): Provides sample code for target image management based on Unity, allowing developers to implement their own methods for capturing and uploading target images.

Running the sample code

The following is an example of Java sample code usage. Fill in your own checklist items in the sample code and then run Main.

m1-java

Next topics:

Note

In the actual workflow, creating target images is recommended to follow best practices. It is advised to read carefully.