The Agartala Smart City Beneficiary Payment Status API looks up whether a payment recorded against a land plot in Agartala has been made, using the plot's LGD village code and plot number. A lookup returns the paymentStatus, transactionId, amount, and paymentDate for that plot, in the application/vnd.taxsaas.v1+json media type. The spec describes a UAT deployment on the MapmyIndia staging host, where a client-credentials token call issues the access token that the lookup sends in its Authorization header.
The Agartala Smart City Mauja and Plot Number API takes a mauja's LGD village code and a plot number and returns the payment record held for that plot in Agartala. Although the title refers to property id details, version 1.0.1 of the published spec exposes one data lookup, the beneficiary payment status call, which returns paymentStatus, transactionId, amount, and paymentDate rather than a property id. It runs on the MapmyIndia UAT staging host, and a client-credentials token call issues the access token that the lookup sends in its Authorization header.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapmyindia.in" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapmyindia.in" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.