Schema Registry Created Successfully but not listed

Hi Everyone,
I was able to create a schema as follows:


    "$schema": "",

    "description": "Schema for an example event",

    "self": {

        "vendor": "com.example",

        "name": "example_event_2",

        "format": "jsonschema",

        "version": "1-0-0"


    "type": "object",

    "properties": {

        "name": {

            "type": "string",

            "maxLength": 128


        "job_role": {

             "type": "string",

            "maxLength": 128



    "additionalProperties": false,

    "required": [




I was using the corresponding apikey.
I had this response:

    "message": "Schema created",
    "updated": false,
    "location": "iglu:com.frontiers/example_event_2/jsonschema/1-0-0",
    "status": 201

Now, Im trying to list all the schemas, but it returns empty array [ _ ]

But If I try to insert it again, it returns that is already created.

The Docker logs of the container returns:

WARNING: Published ports are discarded when using host network mode
[ioapp-compute-1] INFO com.snowplowanalytics.iglu.server.Server - Initializing server with following configuration: {"database":{"username":"postgres","host":"","enableStartupChecks":true,"dbname":"igludb","port":5432,"driver":"org.p
althy":false,"webhooks":[],"debug":true,"superApiKey":"******","preTerminationPeriod":"1 second","swagger":{"baseUrl":""},"repoServer":{"interface":"","port":8080,"idleTimeout":null,"maxConnections":null,"threadPool":{"size":4,"type":"
[pool-2-thread-1] INFO com.zaxxer.hikari.HikariDataSource - iglu-hikaricp-pool - Starting...
[pool-2-thread-1] INFO com.zaxxer.hikari.HikariDataSource - iglu-hikaricp-pool - Start completed.
[ioapp-compute-1] INFO org.http4s.server.blaze.BlazeServerBuilder - 
  _   _   _        _ _
 | |_| |_| |_ _ __| | | ___
 | ' \  _|  _| '_ \_  _(_-<
 |_||_\__|\__| .__/ |_|/__/
[ioapp-compute-1] INFO org.http4s.server.blaze.BlazeServerBuilder - http4s v0.21.22 on blaze v0.14.15 started at http://[::]:8080/

Is strange cause I created this in another VM and I had no issues :frowning:

Thank you

Hey @FabianEpic,

May I ask if you tried to fetch individual schema also ? Was it successful ?

Another possibility might be that you made your schema private but you are listing public schemas without passing api key to your get request. Can you try to pass api key to get request ? This concept is explained here.

Indeed my mistake, the apikey was wrong. Now it’s listing fine. Sorry and thank you.

1 Like

Hi @FabianEpic
Thanks for updating - helps everyone!