---
title: "How do I update my Solr schema on Acquia Search powered by SearchStax?"
date: "2026-07-23T16:32:27+00:00"
summary: "Learn how to update your Solr schema on Acquia Search via the Solr Schema API—with commands, auth steps, and examples."
image:
type: "article"
url: "/acquia-cloud-platform/help/98676-how-do-i-update-my-solr-schema-acquia-search-powered-searchstax"
id: "4c86c53c-44fe-49c8-ae9f-796af12fca2e"
---

Acquia Search powered by SearchStax does not support the upload of schema or configset files. To update Solr schema, you must use Solr Schema API.

Updating Solr schema through Solr Schema API
--------------------------------------------

Important

Access to Schema API may be restricted to Premier or Premier Plus subscription tiers.

For advanced changes, use Solr Schema API by sending POST requests to the `/schema/` endpoint with the authentication token of the account. For more information, visit [Solr Schema API documentation](https://solr.apache.org/guide/solr/latest/indexing-guide/schema-api.html).

### Supported commands

Send these commands as JSON in a POST request to `/schema/`:

Command

Description

`add-field`

Adds a new field.

`delete-field`

Deletes a field.

`replace-field`

Replaces an existing field with a new configuration.

`add-dynamic-field`

Adds a new dynamic field rule.

`delete-dynamic-field`

Deletes a dynamic field rule.

`replace-dynamic-field`

Replaces an existing dynamic field rule.

`add-field-type`

Adds a new field type.

`delete-field-type`

Deletes a field type.

`replace-field-type`

Replaces an existing field type.

`add-copy-field`

Adds a new copy field rule.

`delete-copy-field`

Deletes a copy field rule.

You can include multiple commands in a single POST request. The system handles them in the specified order.

### Authentication

All Schema API requests require an authorization token. Obtain the token from the Search API section on the SearchStax application dashboard. For additional information, refer to [SearchStax Studio Search API](https://www.searchstax.com/docs/searchstudio/searchstax-studio-search-api/).

### Example: Change a tokenizer on a field type

1.  **Retrieve the current field type definition**  
    To obtain the existing definition, run this curl command:
    
        curl -H "Authorization: Token YOUR_AUTH_TOKEN" \
        "https://YOUR_SEARCHSTAX_ENDPOINT/schema/fieldtypes/text_unstemmed_sv?wt=json"
    
    The command returns the full field type definition including analyzers and tokenizers:
    
        {
              "fieldType": {
                "name": "text_unstemmed_sv",
                "class": "solr.TextField",
                "positionIncrementGap": "100",
                "queryAnalyzer": {
                  "tokenizer": {
                    "class": "solr.WhitespaceTokenizerFactory"
              }
            }
          }
        }
    
2.  **POST the updated definition**
    
    To change the tokenizer from WhitespaceTokenizerFactory to StandardTokenizerFactory, use the `replace-field-type` command to send the full updated field type definition:
    
        curl -X POST \
              -H "Authorization: Token YOUR_AUTH_TOKEN" \
              "https://YOUR_SEARCHSTAX_ENDPOINT/schema" \
              -d '{
                "replace-field-type": {
                  "name": "text_unstemmed_sv",
                  "class": "solr.TextField",
                  "positionIncrementGap": "100",
                  "queryAnalyzer": {
                    "tokenizer": {
                      "class": "solr.StandardTokenizerFactory"
                    }
                  }
                }
              }'
    
    A successful response returns:
    
        {
              "responseHeader": {
                "status": 0,
                "QTime": 3565
              }
            }
    

Run the GET request from step 1 again to ensure that the change is correct.

Limitations
-----------

*   New files such as stopwords, synonyms, and protwords that are not in the current schema definition cannot be uploaded. You can only refer to files already in the configset.
*   Manage synonyms and stopwords through the SearchStax UI.
*   Contact SearchStax Support for assistance with the deployment of other text files such as protwords, accents, stoptags, and user dictionaries.

Additional tools
----------------

SearchStax provides a Python-based schema management tool that wraps the Schema API for common operations. Access the tool at: [https://github.com/searchstax/searchstax-schema-management/](https://github.com/searchstax/searchstax-schema-management/).

Note

This tool might not support all use cases. For example, to change tokenizers, you must use direct API calls.