Developer API overview
Addons extend Claimo by registering new requirement types. A type is just a key (used
in a voucher file) bound to a factory that builds a Requirement. This means you can add
checks Claimo doesn’t ship — a social-media follow, a web-API lookup, a Discord role —
without forking the plugin.
Depend on Claimo
Section titled “Depend on Claimo”repositories { maven("https://repo.vao.zone/releases") // or /snapshots for -SNAPSHOT versions}dependencies { compileOnly("zone.vao:claimo-api:1.4.2")}repositories { maven { url 'https://repo.vao.zone/releases' } // or /snapshots for -SNAPSHOT versions}dependencies { compileOnly 'zone.vao:claimo-api:1.4.2'}<repositories> <repository> <id>vao-releases</id> <url>https://repo.vao.zone/releases</url> <!-- or https://repo.vao.zone/snapshots for -SNAPSHOT versions --> </repository></repositories>
<dependencies> <dependency> <groupId>zone.vao</groupId> <artifactId>claimo-api</artifactId> <version>1.4.2</version> <scope>provided</scope> </dependency></dependencies>depend: [Claimo] # or softdepend: [Claimo]The three steps
Section titled “The three steps”- Implement a
Requirement— an async check that returns satisfied / unsatisfied. - Register the type from your
onEnable, optionally declaring input fields so it shows up in the in-game creator. - Use it in a voucher by its type key.
Each step has its own page:
Custom requirementsImplement and register a requirement type.
EventsReact to redemptions — cancel or observe them.
API referenceThe full ClaimoApi surface.