LogoLogo
Abscan
Abscan
  • Introduction
  • ✨Getting Started
    • Creating an Account
    • Getting an API key
    • Endpoint URLs
  • 🎯API Endpoints
    • Accounts
    • Contracts
    • Transactions
    • Blocks
    • Logs
    • Geth/Parity Proxy
    • Tokens
    • Stats
  • 🤝Support
    • FAQ
    • Rate Limits
    • Common Error Messages
    • Getting Help
  • Visit Abscan.org
Powered by GitBook
On this page
  • 1. Using the Verify Contract Endpoint
  • 2. Specify Your chainId
  • 3. Add Contract Source Code
  • 4. Add Contract Metadata
  • 5. Submitting Verification
Export as PDF
  1. Contract Verification

Multichain Verification

Last updated 5 months ago

For repeated or multichain contract verification, it's best to use the to automate source code submission .

You may specify a chainId along with an to submit verification for any Abscan-like explorer

1. Using the Verify Contract Endpoint

In Postman, set your request method to HTTP POST and your URL to https://api.abscan.org/api .

Under the Body tab and using form-data, specify the "module" to contract and "action" to verifysourcecode.

All API based verification must be authenticated, include your under the "apikey" field.

2. Specify Your chainId

Select the chain you've deployed your contract, which is supported by an Abscan-like explorer.

Specify it under the "chainId" parameter, such as 1 for Ethereum and 8453 for Base.

3. Add Contract Source Code

We support 2 formats, solidity-single-file or solidity-standard-json-input.

Paste your source code under "sourceCode" and the code format under the "codeformat" parameter.

4. Add Contract Metadata

Include the contract address as "contractaddress", beginning with "0x".

Specify your contract file path and contract name separated by a colon as "contractname", such as "contracts/Verified.sol:Verified".

5. Submitting Verification

Using JSON is the gold standard for verification, as you can ( if you use imports such as from ).

Optionally if your contract uses , you may specify them too under the "constructorArguments" parameter in format.

Select the compiler version used from as your "compilerversion".

Click Send and you'll receive a guid which you can then .

Alternatively if everything went well, you'll see the happy green checkmark on your

✅
✨
include compiler settings and multiple files
OpenZeppelin
constructor arguments
ABI encoded
this list
✅
contract code
🐇
Abscan API key
Abscan API key
check on your verification status
Verify Contract endpoint