How to design typescript model for response?

A class is unsuitable for declaring a type that represents an HTTP response. Use interface or type instead because the deserialized JSON values that result from HTTP requests will never be instances of a class

@Angular StyleGuide
Consider using an interface for data models.

export interface Model{
        id: number;
        name: string;
    }

export interface ResponseModel{
         data:Array<Model>;
  }

getInfo(): Observable<responseModel>{
return this._httpClient.get<resposneModel>('url);
}

data should have type model[] and whole response type is responseModel

export class responseModel{
   data:model[];
}
export class model{
  name:string;
  id: number;
}

getInfo(): Observable<responseModel> {
// API HTTP Call
}

I think this is a subjective question so I'll share my experiences when I was having a similar situation.

All of the backend endpoints for my project responses with { data: THE_DATA_OBJECT }. I think it's a bit redundant to design all of my response models starts with a "data" prefix, so instead of doing that, I basically unwrap the "data" prefix in my api service.

Something like the following:

genericHttpCall<T>(path: string, method: string, params: any}: Observable<T> {
  return this.httpClient.request().pipe(map(response => response.data));
}

So basically that saves me from doing class responseModel<T> so that I can focus on design the real model freely instead of let backend affect my model structure.

Also, I always use interface instead of class for response model because they are plain data model that involves no constructor or methods. Unless you want to make the model works for your business logic.